Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...'
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
"David G. Johnston" <david.g.johnston@gmail.com>,
"zedaardv@drizzle.com" <zedaardv@drizzle.com>,
"pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2023-02-23T21:07:10Z
Lists: pgsql-bugs
Attachments
- v4-0001-Disallow-NULLS-NOT-DISTINCT-indexes-for-primary-k.patch (application/octet-stream) patch v4-0001
> On 16 Dec 2022, at 19:19, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Daniel Gustafsson <daniel@yesql.se> writes: >> Oh, ok, if so then I misunderstood. No worries, v2 is then the one to consider. > > I'm good with v2. Returning to an old thread that got sidetracked by christmas et.al. Attached is a rebased v4 based on the v2 patch above. I'll attach this to the CF to get the full CFbot treatment and if all is green I'll push this. -- Daniel Gustafsson
Commits
-
Disallow NULLS NOT DISTINCT indexes for primary keys
- d9595232579a 16.0 landed