From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | Devrim Gündüz <devrim(at)gunduz(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Renaming of pg_xlog and pg_clog |
Date: | 2016-08-26 14:36:43 |
Message-ID: | 47eda150-4789-da62-315a-35a9eda9cebc@timbira.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 26-08-2016 09:25, Devrim Gündüz wrote:
> On Fri, 2016-08-26 at 21:12 +0900, Michael Paquier wrote:
>> In short, with the current names, sometimes users think that pg_xlog
>> and pg_clog are just logs. And so it is fine to delete them to free up
>> space, corrupting their cluster, because they are just *logs*.
>
> ...and we also have "pg_logical", that includes a "log" keyword already...
>
"clog" and "xlog" is almost "log"; "logical" is not. I don't imagine
people confusing "logical" meaning "log".
--
Euler Taveira Timbira - http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-08-26 14:44:54 | Re: Renaming of pg_xlog and pg_clog |
Previous Message | Tom Lane | 2016-08-26 14:35:35 | Re: PG_DIAG_SEVERITY and a possible bug in pq_parse_errornotice() |