Re: pg_dump losing index column collations for unique and primary keys - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_dump losing index column collations for unique and primary keys
Date
Msg-id 20212.1575474538@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump losing index column collations for unique and primarykeys  (Alexey Bashtanov <bashtanov@imap.cc>)
List 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



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16148: Query on Large table hangs in ETL flows and gives out of memory when run in pgAdmin4
Next
From: Chris Bandy
Date:
Subject: Re: BUG #16041: Error shows up both in pgAdmin and in Ruby (pg gem) -Segmentation fault