| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Renaming of pg_xlog and pg_clog |
| Date: | 2016-08-30 00:58:01 |
| Message-ID: | 0698dcf1-3588-c902-fef2-148354b4a60c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/28/16 8:45 PM, Jim Nasby wrote:
> People accidentally blowing away pg_clog or pg_xlog is a pretty common
> occurrence, and I don't think there's all that many tools that reference
> them. I think it's well worth renaming them.
I think a related problem is that the default log directory is called
"pg_log", which is very similar to those other two. There is no quick
way to tell their meaning apart.
I would consider changing the default from "pg_log" to "log". Then we'd
also be at the point where we can say, everything starting with "pg_" is
internal, don't touch it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2016-08-30 01:07:25 | Re: [PATCH] Send numeric version to clients |
| Previous Message | Peter Eisentraut | 2016-08-30 00:54:33 | Re: Renaming of pg_xlog and pg_clog |