| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joel Jacobson <joel(at)trustly(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog -> pg_xjournal? |
| Date: | 2016-05-04 02:35:26 |
| Message-ID: | 57295FEE.3040609@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/03/2016 06:38 PM, Michael Paquier wrote:
> On Mon, May 2, 2016 at 10:29 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Thu, Apr 28, 2016 at 11:46 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
>>> I just helped another person yesterday who deleted their pg_xlog.
>>
>> The biggest reason I've seen pg_xlog get deleted is not because it's
>> called pg_xlog, but because it's located someplace other than under
>> the data directory and referenced via a symlink. Renaming it might
>> still make it less likely for people to get trigger happy, though.
>
> FWIW, I have seen a couple of times the same pattern as Craig:
> "because it contains log in its name implies that removing it causes
> no harm".
"You can't fix stupid.", Ron White.
That said, I too have run into the "Oh it said, log... we thought it was
o.k. to delete."
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2016-05-04 02:55:53 | text search changes vs. binary upgrade |
| Previous Message | Michael Paquier | 2016-05-04 01:38:52 | Re: pg_xlog -> pg_xjournal? |