| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | Nick Dro <postgresql(at)walla(dot)co(dot)il>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Postgresql gives error that role goes not exists while it exists |
| Date: | 2017-10-05 13:19:18 |
| Message-ID: | CA+TgmoYDrtJQFOxzkkZiKzuPN3dv__-+qbeRQVc2B+_6pk9VKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 3, 2017 at 8:47 AM, Euler Taveira <euler(at)timbira(dot)com(dot)br> wrote:
> I'm not sure. I bet a dime that the role was created as "Iris" and you
> are trying to assing "iris" (they are different). If you list the
> roles, we can confirm that.
I don't see how this would explain anything. "current_role"() is
going to return the role using its actual case, and that's also what
pg_hash_role() expects.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2017-10-05 13:28:07 | v10 bottom-listed |
| Previous Message | Michael Paquier | 2017-10-05 12:51:49 | Re: cache lookup errors for missing replication origins |