Re: pg_dump losing index column collations for unique and primary keys
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexey Bashtanov <bashtanov@imap.cc>
Cc: pgsql-bugs@postgresql.org
Date: 2019-12-04T15:48:58Z
Lists: pgsql-bugs
Alexey Bashtanov <bashtanov@imap.cc> writes: > What do you think of making pg_dump warn the user if they are trying > to dump a weird PK/UK which has collations in index and column not matching? > And maybe even throw an error in case of --binary-upgrade? I can't get excited about spending any additional effort on this issue. If I thought it were actually happening in the field to any significant extent, I'd be more interested in supporting the case instead of just disallowing it. But I think the actual occurrences are epsilon, so there are better places to be spending our time. regards, tom lane
Commits
-
Disallow non-default collation in ADD PRIMARY KEY/UNIQUE USING INDEX.
- fbbf68094c5f 13.0 landed