Re: Renaming of pg_xlog and pg_clog - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 2f3b9ce6-3084-068a-a2b9-0276c7eab6c4@commandprompt.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 08/26/2016 03:48 AM, Magnus Hagander wrote:

>
> Same reason I'm also +1 for Stephens suggestion to put all things that
> should not be in a base backup into the same directory. That may break
> things now, but it will simplify things down the road. And doing it at
> the same time as renaming these things makes a lot of sense, because it
> causes breakage that tool-builders *have* to look at, and then they will
> hopefully also notice the other change.

If this is done this fall, developers will have at least a year to fix 
their utilities.

JD




-- 
Command Prompt, Inc.                  http://the.postgres.company/                        +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
Unless otherwise stated, opinions are my own.



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PG_DIAG_SEVERITY and a possible bug in pq_parse_errornotice()
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Renaming of pg_xlog and pg_clog