From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Disallow unique index on system columns |
Date: | 2016-04-15 01:25:38 |
Message-ID: | 20160415012538.zfyj5s5vvqpaagws@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2016-04-14 21:02:26 -0400, Tom Lane wrote:
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> > I proposed a fix over there, but it didn't go anywhere, probably
> > because Tom and Andres discussed just disallowing unique indexes on
> > system columns altogether. So, the attached patch does just that, and
> > also fixes up the replica identity bugs too, as it's still possible
> > that someone could create a unique index on a system column with an
> > old version, upgrade, then try to set the replica identity to that
> > index. We'd need to handle that correctly, so I fixed that too.
>
> AFAIR, what we were discussing was disallowing any index on a system
> column (other than OID). I do not see why only unique indexes are
> problematic for them; the semantic issues are independent of that.
+1
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2016-04-15 01:26:35 | Re: Disallow unique index on system columns |
Previous Message | Craig Ringer | 2016-04-15 01:17:54 | Re: Pglogical questions and problems |