| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-10-14 04:38:06 |
| Message-ID: | 071f8400-b966-1a0b-9066-e5bb789189d7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/12/16 11:22 AM, Tom Lane wrote:
> The main problem we're trying to fix here is people thinking that
> something with "log" in the name contains discardable data. Just
> relocating the directory without renaming it won't improve that.
I think it would help if we moved it to something like
"internal/pg_xlog" and "internal/pg_clog". Keep the name but move it
out of sight.
We have a tool called pg_xlogdump in the standard installation. initdb
has an option --xlogdir, pg_basebackup has --xlog and others. Renaming
the xlog directory would make this all a bit confusing, unless we're
prepared to rename the programs and options as well.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-10-14 05:02:07 | Re: PATCH: Batch/pipelining support for libpq |
| Previous Message | Ashutosh Bapat | 2016-10-14 04:37:05 | Re: Partition-wise join for join between (declaratively) partitioned tables |