Re: xlog file naming

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: xlog file naming
Date: 2012-08-23 13:29:55
Message-ID: 10309.1345728595@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On Tue, 2012-08-21 at 12:01 -0400, Robert Haas wrote:
>> It's possible there's something we want to change here, but it's far
>> from obvious what that thing is. Our WAL file handling is
>> ridiculously hard to understand, but the problem with changing it is
>> that there will then be two things people have to understand, and a
>> lot of tools that have to be revamped. It isn't clear that it's worth
>> going through that kind of pain for a minor improvement in clarity.

> The idea was that since we already broke some tools, possibly silently
> (...FF files that they previously skipped), a more radical renaming
> might break those tools more obviously, and make some other things
> simpler/easier down the road.

I think we already had that discussion, and the consensus was that
we did not want to break WAL-related tools unnecessarily. If there
were a high probability that the FF change will actually break tools in
practice, the conclusion might have been different; but nobody believes
that there is much risk there.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-08-23 13:36:23 Re: new --maintenance-db options
Previous Message Andrew Dunstan 2012-08-23 12:53:23 Re: alter enum add value if not exists