Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...' - Mailing list pgsql-bugs

Daniel Gustafsson <daniel@yesql.se> writes:
> The attached prohibits the use of NULLS NOT DISTINCT for backing primary key
> constraints but allow them for unique constraints.  Is this along the lines of
> what you had in mind?

Needs more than zero comments in the code, and why bother testing
is_alter_table in index_check_primary_key?  We're disallowing
this case across-the-board, no matter how you get to it.

I'll defer to Peter on whether this is in fact the right way to go,
or we should relax the syntax restriction as David suggests.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Alex Richman
Date:
Subject: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1
Next
From: Amit Kapila
Date:
Subject: Re: Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1