Error messages on duplicate schema names

From: Andrus <kobruleht2(at)hot(dot)ee>
To: pgsql-general(at)postgresql(dot)org
Subject: Error messages on duplicate schema names
Date: 2021-01-06 17:15:24
Message-ID: ae2a7dc1-9d71-8cba-3bb9-e4cb7eb1f44e@hot.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!

ALTER DEFAULT PRIVILEGES IN SCHEMA public,public   GRANT all ON TABLES
TO testoig;

Throws strange error

Tuple already updated by self

In other case which I posted duplicate schema causes another strange error

duplicate key value violates unique constraint
"pg_default_acl_role_nsp_obj_index"DETAIL: Key (defaclrole,
defaclnamespace, defaclobjtype)=(30152, 186783649, r) already exists.

Should duplicate schema names accepted or should their usage throw
better error messages.

Andrus.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rob Northcott 2021-01-06 17:28:57 Keep needing to run manual analyze
Previous Message Stephen Frost 2021-01-06 17:14:02 Re: LDAP(s) doc misleading