Robert Haas writes:
> On Tue, Oct 3, 2017 at 8:47 AM, Euler Taveira 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.
On Tue, Oct 3, 2017 at 8:47 AM, Euler Taveira 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 t
Craig Ringer writes:
> We could only emit a useful HINT if we actually went and looked in the
> relevant catalog for a different-cased version. Which is pretty
> expensive.
There is actually a hint somewhat like that for the specific case of
misspelled column names in DML statements:
postgres=#
On 3 October 2017 at 20:47, Euler Taveira wrote:
>
> 2017-10-03 5:49 GMT-03:00 Nick Dro :
> > Can someone assists with the issue posted on StackOverflow?
> >
> > https://stackoverflow.com/questions/46540537/postgresql-9-3-creation-of-group-role-causes-permission-problems
> >
> >
> > Creation of ne
2017-10-03 5:49 GMT-03:00 Nick Dro :
> Can someone assists with the issue posted on StackOverflow?
>
> https://stackoverflow.com/questions/46540537/postgresql-9-3-creation-of-group-role-causes-permission-problems
>
>
> Creation of new Group Role causes postgresql to think that Login roles does
> no
Can someone assists with the issue posted on StackOverflow?
https://stackoverflow.com/questions/46540537/postgresql-9-3-creation-of-group-role-causes-permission-problems
Creation of new Group Role causes postgresql to think that Login roles does not exist. I think it's a bug? or at least a wr