From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: PostgreSQL Bugs <pgsql-bugs@postgresql.org>
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
Date: Fri, 20 Jun 2014 14:24:55 -0400
Message-ID: <9690.1403288695@sss.pgh.pa.us> (raw)
In-Reply-To: <20140620181104.GF29143@momjian.us>
References: <20140619020633.GA20469@momjian.us>
<20140619015205.GD3806@momjian.us>
<20140619014034.GC3806@momjian.us>
<20140619220425.GQ18688@eldon.alvh.no-ip.org>
<20140619221240.GC27747@eldon.alvh.no-ip.org>
<20140620171915.GC29143@momjian.us>
<20140620173351.GV18688@eldon.alvh.no-ip.org>
<8519.1403286102@sss.pgh.pa.us>
<20140620181104.GF29143@momjian.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>
Bruce Momjian <bruce@momjian.us> writes:
> On Fri, Jun 20, 2014 at 01:41:42PM -0400, Tom Lane wrote:
>> Yeah. In my mind, at least, there's been a TODO for some time for
>> pg_resetxlog to make sure that pg_clog and the other SLRU-like files
>> get populated appropriately when you tell it to change those counters.
>> You have to have a segment file at the right place or startup fails.
> Well, if we are going to do this, we had better do all cases or the
> behavior will be quite surprising, and when doing disaster recovery,
> surprises are not good. I am a little worried that removing files as
> part of pg_resetxlog might cause data to be lost as users try to figure
> things out.
Huh? The basic charter of pg_resetxlog is to throw away files, ie, all
of your WAL.
But in this case what we're talking about is a secondary function, namely
the ability to move the XID, MXID, etc counter values. Up to now, if you
did that, it was on your head to manually create appropriate SLRU segment
files. It's certainly less error-prone, not more so, if the code were
to take care of that for you.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, alvherre@2ndquadrant.com, andres@2ndquadrant.com
Subject: Re: pg_upgrade < 9.3 -> >=9.3 misses a step around multixacts
In-Reply-To: <9690.1403288695@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox