| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-08-29 16:09:24 |
| Message-ID: | 20160829160924.26nt7vq3jb4sjqez@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-08-29 16:24:59 | Re: [COMMITTERS] pgsql: Fix pg_receivexlog --synchronous |
| Previous Message | David Steele | 2016-08-29 16:07:51 | Re: Renaming of pg_xlog and pg_clog |