Re: pg_dump losing index column collations for unique and primary keys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexey Bashtanov <bashtanov(at)imap(dot)cc>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_dump losing index column collations for unique and primary keys
Date: 2019-12-04 15:48:58
Message-ID: 20212.1575474538@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alexey Bashtanov <bashtanov(at)imap(dot)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

In response to

Browse pgsql-bugs by date

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