| From: | "Hans Buschmann" <buschmann(at)nidsa(dot)net> |
|---|---|
| To: | "Peter Geoghegan" <pg(at)bowt(dot)ie> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL mailing lists" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14844: Failure/Duplicate key value with ALTER DATABASE set search_path |
| Date: | 2017-10-09 08:26:41 |
| Message-ID: | D2B9F2A20670C84685EF7D183F2949E2373E02@gigant.nidsa.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I run the above query (also without restricting to pg_catalog) under superuser postgres in both dbs.
There was no error.
The databases are on SSD, no problems with storage so far (checksums are enabled).
I only did standard SQL/utility commands to create, restore, set_search_path and analyze the 2 databases one after another without any error.
The first error that occurred was that the second alter database set search_path was executed without error, but had no effect!
Then afterwords other alter database set search_path commands gave the error of duplicate key.
The procedure is quite easy and straight forward: only create/restore/set_search_path/analyze 2 databases which have objects in other schemas as public.
The database size is about 1 GB in PG_DATA each.
If necessary, I can repeat the procedure on another machine, but please give me some time.
Thank you
Hans Buschmann
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2017-10-09 14:13:41 | 10.0: Logical replication doesn't execute BEFORE UPDATE OF <columns> trigger |
| Previous Message | Peter Geoghegan | 2017-10-08 22:47:53 | Re: BUG #14844: Failure/Duplicate key value with ALTER DATABASE set search_path |