Re: BUG #14844: Failure/Duplicate key value with ALTER DATABASE set search_path

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: buschmann(at)nidsa(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14844: Failure/Duplicate key value with ALTER DATABASE set search_path
Date: 2017-10-06 14:48:51
Message-ID: 6266.1507301331@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

buschmann(at)nidsa(dot)net writes:
> When trying to change or reset the search path the following error occurs
> (PG 10.0):

> didisdb=# ALTER DATABASE xxxdb SET search_path TO public,xxxo,xxxp;
> ERROR: duplicate key value violates unique constraint
> "pg_db_role_setting_databaseid_rol_index"
> DETAIL: Key (setdatabase, setrole)=(19084, 0) already exists.

I tried to reproduce this, but could not. Can you reconstruct the
exact sequence of commands you issued to get here?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-10-06 14:54:21 Re: BUG #14845: postgres_fdw and mysql_fdw can cause crash of instance
Previous Message Tom Lane 2017-10-06 14:27:12 Re: Bug in Postgresql 10.0: regexp functions return invalid cach ID: 42