Re: [HACKERS] Potential data loss of 2PC files - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Potential data loss of 2PC files
Date
Msg-id CAB7nPqTPfQp4fooiYfJeQx=-9-k3+tuP57iEbgr1DD6CHwf+wg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Potential data loss of 2PC files  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Potential data loss of 2PC files  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
On Fri, Mar 24, 2017 at 5:08 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:
> Hmm, it doesn't work (but appplies) on current HEAD:
> [...]
> Data page checksums are disabled.
>
> fixing permissions on existing directory /spool/pg_data ... ok
> creating subdirectories ... ok
> selecting default max_connections ... 100
> selecting default shared_buffers ... 128MB
> selecting dynamic shared memory implementation ... posix
> creating configuration files ... ok
> running bootstrap script ... 2017-03-23 23:07:14.705 MSK [40286] FATAL:
> could not open file "pg_clog": No such file or directory
> child process exited with exit code 1
> initdb: data directory "/spool/pg_data" not removed at user's request

And the renaming of pg_clog to pg_xact is also my fault. Attached is
an updated patch.
-- 
Michael

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] WIP: Faster Expression Processing v4
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] pg_dump, pg_dumpall and data durability