[HACKERS] Postgresql gives error that role goes not exists while it exists

[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 not exist. I think it's a bug? or at least a wrong error message
 

[HACKERS] Possible bug in 9.3.17 using operator <>

[Nick Dro]

The operator <> seems to not work properly comparing citext types in triggers function.
 
https://stackoverflow.com/questions/45441840/posgresql-9-3-operator-doesnt-give-logical-result
 
Can someone figure out what is the problem? This seems like a bug.

[HACKERS] Error log for psql (uploading backup) in PostgreSQL 9.3.17

[Nick Dro]

Hi,
I should say that I'm haviing this issue since 9.3.2 I though it would be resolved when I upgrade to 9.3.17 but this still appear.
This is a very wierd issue.
 
I upload backups using pg_restore and
psql -h SERVER -U USERNAME -f backup.sql -q -d databasename -pPORT 2>errors.txt >output.txt
 
When I open the errors.txt file I see:
 
psql:backup.sql:43112523: ERROR:  relation "tablename" does not existLINE 3: from tablename ^QUERY:  select tablenameidfrom tablenamejoin tablename_visable v using(statusid)where id=$1 order by id,case statusidwhen 2 then 1 when 1 then 2 else 3 end, coalesce(rev,'-1') desclimit 1
 
 
Now, the intresting thing is that tablename exists in the backup.
I can do:
select * from tablename
The table is OK, the data is OK. So I don't understand this error.
 
It looks like a wrong order of commands, maybe the creation of the table is done after it creates this code?
 
Why is this happens?