From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
Subject: | Re: pg_constraint.conincluding is useless |
Date: | 2018-09-07 20:02:57 |
Message-ID: | 20180907200257.bxciigkvxd7fsct2@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-Sep-07, Bruce Momjian wrote:
> On Sun, Sep 2, 2018 at 01:27:25PM -0400, Tom Lane wrote:
> > Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > > This requires a catversion bump, for which it may seem a bit late;
> > > however I think it's better to release pg11 without a useless catalog
> > > column only to remove it in pg12 ...
> >
> > Catversion bumps during beta are routine. If we had put out rc1
> > I'd say it was too late, but we have not.
> >
> > If we do do a bump for beta4, I'd be strongly tempted to address the
> > lack of a unique index for pg_constraint as well, cf
> > https://www.postgresql.org/message-id/10110.1535907645@sss.pgh.pa.us
>
> Uh, if we add a unique index later, wouldn't that potentially cause
> future restores to fail? Seems we better add it now.
Committed on Sep 4th as 17b7c302b5fc.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-09-07 20:12:29 | Re: A strange GiST error message or fillfactor of GiST build |
Previous Message | Bruce Momjian | 2018-09-07 19:48:29 | Re: pg_constraint.conincluding is useless |