| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-08-26 21:11:00 |
| Message-ID: | f9cab8fb-f3de-7208-fbe9-96cda0d804c6@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/26/16 12:28 PM, Tom Lane wrote:
> Also, I'd just as soon not move/rename things
> that don't really need it.
I'm just as happy with not changing anything. But if we're going to
rename stuff, let's at least think about something slightly more
comprehensive. Any rename is going to break a bunch of stuff. But if
we break it in a way that reduces the need for future discussion or
changes, it would at least be a small win in the long run.
> If, for example, we decide to move
> postgresql.conf to etc/postgresql.conf, that is going to break a metric
> ton of stuff that doesn't need to get broken AFAICS.
Sure, I'd be content with leaving those in the top-level instead of say
"etc".
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-08-26 21:13:07 | Re: Why is a newly created index contains the invalid LSN? |
| Previous Message | Andres Freund | 2016-08-26 21:08:30 | Re: Renaming of pg_xlog and pg_clog |