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-03T18:24:38Z
Lists: pgsql-bugs
Attachments
- disallow-collation-mismatch-in-ADD-USING-INDEX.patch (text/x-diff) patch
I wrote: > In short, I'd say the bug here is not pg_dump's fault at all, > but failure to insist on collation match in ADD PRIMARY KEY > USING INDEX. Concretely, I think we should do the attached. I'm not quite sure whether we should back-patch this, though. It's been wrong since we added collations, but the main impact of a back-patch might be to break cases that were working more or less okay for people. A compromise idea is to back-patch only into v12, where the issue became quite a lot more important due to nondeterministic collations. Thoughts? regards, tom lane
Commits
-
Disallow non-default collation in ADD PRIMARY KEY/UNIQUE USING INDEX.
- fbbf68094c5f 13.0 landed