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

From Andres Freund
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 20160829160924.26nt7vq3jb4sjqez@alap3.anarazel.de
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On 2016-08-29 12:07:51 -0400, David Steele wrote:
> >> pg_replslot -> pg_tmp/pg_repslot
> > 
> > That's most certainly not ephemeral. Just because something isn't
> > generally appropriate on a standby, doesn't, by far, mean it's ephemeral.
> 
> Yes, ephemeral was a poor choice of words.  I really meant "can be
> excluded from backups".

Then it most certainly can't be called pg_tmp, that'll just invite
people to rm -rf it. And then they'll be screwed.



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Renaming of pg_xlog and pg_clog
Next
From: Bruce Momjian
Date:
Subject: Re: [COMMITTERS] pgsql: Fix pg_receivexlog --synchronous