Re: On-disk compatibility for nbtree-unique-key enhancement

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: On-disk compatibility for nbtree-unique-key enhancement
Date: 2018-09-28 15:00:38
Message-ID: caab10bb-6361-273f-93ac-8fc0c9737443@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21/09/2018 01:18, Peter Geoghegan wrote:
> * This means that there is a compatibility issue for anyone that is
> already right on the threshold -- we *really* don't want to see a
> REINDEX fail, but that seems like a possibility that we need to talk
> about now.

When would the REINDEX need to happen? Will the code still be able to
read and write v3 btrees? Could there perhaps be an amcheck or
pageinspect feature that tells you ahead of time if there are too large
items in an old index?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-09-28 15:04:34 Re: C99 compliance for src/port/snprintf.c
Previous Message Peter Eisentraut 2018-09-28 14:50:33 Re: Making all nbtree entries unique by having heap TIDs participate in comparisons