Re: Small TRUNCATE glitch - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Small TRUNCATE glitch
Date
Msg-id 20141210010405.GU1768@alvh.no-ip.org
Whole thread Raw
In response to Re: Small TRUNCATE glitch  (Alex Shulgin <ash@commandprompt.com>)
Responses Re: Small TRUNCATE glitch  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
Alex Shulgin wrote:

> The 2PC part requires extending bool flag to fit the trunc flag, is this
> approach sane?  Given that 2PC transaction should survive server
> restart, it's reasonable to expect it to also survive the upgrade, so I
> see no clean way of adding another bool field to the
> TwoPhasePgStatRecord struct (unless some would like to add checks on
> record length, etc.).

I don't think we need to have 2PC files survive a pg_upgrade.  It seems
perfectly okay to remove them from the new cluster at some appropriate
time, *if* they are copied from the old cluster at all (I don't think
they should be.)

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: logical column ordering
Next
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)