From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
---|---|
To: | Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> |
Cc: | Michael Nolan <htfoot(at)gmail(dot)com>, Joel Jacobson <joel(at)trustly(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_xlog -> pg_xjournal? |
Date: | 2015-06-02 14:35:31 |
Message-ID: | CA+HiwqEd0_D4j38CB4JvZkrn6xjDK_oZwq3SHD7XtHSe9+oRxg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 2, 2015 at 11:03 PM, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com> wrote:
> At 2015-06-01 23:35:23 -0500, htfoot(at)gmail(dot)com wrote:
>>
>> No, it won't prevent the incredibly stupid from doing incredibly
>> stupid things, nothing will.
>
> I hate to speechify, but I think we should try hard to avoid framing
> such questions in terms of "incredibly stupid" people and the things
> they might do.
>
> We have anecdotal and circumstantial evidence that the names pg_xlog and
> pg_clog have given some people the impression that they can delete files
> therein. Sometimes do this when their server is in imminent danger of
> running out of space, sometimes not. But our documentation makes it
> clear that these files are important.
>
> I think naming these directories to convey the right impression is a
> straightforward interface design problem, and we also know that big
> flashing red warnings are less effective than one might hope for. I
> do not think a bigger, stripier warning is worth doing in isolation.
> I do think it's worth choosing better names.
>
+1.
Regards,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-06-02 14:37:59 | Re: nested loop semijoin estimates |
Previous Message | Bruce Momjian | 2015-06-02 14:20:52 | Re: pg_xlog -> pg_xjournal? |