Re: BUG #14701: pg_dump fails to dump pg_catalog schema

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: neil(at)postgrescompare(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14701: pg_dump fails to dump pg_catalog schema
Date: 2017-06-13 12:57:26
Message-ID: aef9d070-4be0-c2ed-434e-354b5275e27e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 6/12/17 12:18, Tom Lane wrote:
> That leads to the idea that it would be okay to let pg_dump print
> "provider = default" but *not* let CREATE COLLATION accept that.
> If we did that and also disallowed cloning the default collation,
> then we'd have the property that only the original default collation
> has provider 'd', and the existing code would continue to work.

Fixed that way.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message balakishan sandeveni 2017-06-13 18:03:42 Error-Report Postgresql
Previous Message Michael Paquier 2017-06-13 09:34:20 Re: [BUGS] Invalid WAL segment size. Allowed values are 1,2,4,8,16,32,64