Re: Disallow unique index on system columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Disallow unique index on system columns
Date: 2016-04-15 01:56:13
Message-ID: 10338.1460685373@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> On 15 April 2016 at 13:30, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> What'd be the point of indexing ctid, and why would it be correct?
>> Wouldn't, hm, HOT break it?

> I don't personally see the point.

An index on ctid is useless by definition: if you know the ctid of
a tuple, you can just go get it, never mind the index.

> Is it worth making some changes to pg_dump to skip such indexes?

No.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-04-15 02:17:02 Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner.
Previous Message David Rowley 2016-04-15 01:43:51 Re: Disallow unique index on system columns