From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Is pg_control file crashsafe? |
Date: | 2016-04-28 21:58:00 |
Message-ID: | 19518802B8BEC076.37020283-1F3D-49F4-9C55-2B7F3F8504E9@mail.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello everyone!
We have some issue with truncated pg_control file on Windows after power failure.My questions is : 1) Is pg_control protected from say , power crash or partial write? 2) How PG update pg_control? By writing in it or writing in some temp file and after that rename it to pg_control to be atomic?3) Can PG have multiple pg_control copy to be more fault tolerant?
PS During some experiments we found that at present time there is no any method to do crash recovery with "restored" version of pg_control (based on some manipulations with pg_resetxlog ). Only by using pg_resetxlog and setting it parameters to values taken from wal file (pg_xlogdump)we can at least start PG and saw that PG state is at the moment of last check point. But we have no real confidence that PG is in consistent state(also docs on pg_resetxlogs told us about it too)
Alex IgnatovPostgres Professional: http://www.postgrespro.comRussian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Sehrope Sarkuni | 2016-04-28 23:03:22 | Re: Add jsonb_compact(...) for whitespace-free jsonb to text |
Previous Message | Andres Freund | 2016-04-28 20:44:23 | Re: 9.6 and fsync=off |