From: Andrus <kobruleht2@hot.ee>
To: pgsql-general@postgresql.org
Subject: Error messages on duplicate schema names
Date: Wed, 6 Jan 2021 19:15:24 +0200
Message-ID: <ae2a7dc1-9d71-8cba-3bb9-e4cb7eb1f44e@hot.ee> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: kobruleht2@hot.ee
Subject: Re: Error messages on duplicate schema names
In-Reply-To: <ae2a7dc1-9d71-8cba-3bb9-e4cb7eb1f44e@hot.ee>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox