Re: pg_xlog -> pg_xjournal?

On 6/2/15 4:58 PM, David Steele wrote:
> On 5/31/15 1:46 PM, Tom Lane wrote:
>> Hm. I think the impact on third-party backup tools would be rather bad,
>> but there's a simple modification of the idea that might fix that:
>> just always create pg_xlog as a symlink to pg_xjournal during initdb.
>> Anybody who blindly removes pg_xlog won't have done anything
>> irreversible. We could deprecate pg_xlog and stop creating the symlink
>> after a few releases, once third-party tools have had a reasonable
>> amount of time to adjust.
>
> As the author of a third-party backup tool I'd prefer to make a clean
> break and just rename the directories in a single release. 9.5 has
> similar backup/restore related changes with no nod to backwards
> compatibility.
>
> And that's fine. Applications can iterate faster than databases and
> they should.

+1. I think we're making a mountain out of a mole-hill and putting any
possibility of improvement here at risk. (And I definitely think this
needs improvement).

> Two options to make lives easier:
>
> 1) An initdb option to create the necessary symlinks as Tom suggests,
> just not by default.
> 2) Instructions in the release notes for users who did not see the
> initdb option in the first place.

#2 seems reasonable. #1 seems like it's partway up the molemountain.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com