| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | PATCH: track last known XLOG segment in control file |
| Date: | 2015-12-12 21:14:13 |
| Message-ID: | 566C8E25.2060706@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
this is the second improvement proposed in the thread [1] about ext4
data loss issue. It adds another field to control file, tracking the
last known WAL segment. This does not eliminate the data loss, just the
silent part of it when the last segment gets lost (due to forgetting the
rename, deleting it by mistake or whatever). The patch makes sure the
cluster refuses to start if that happens.
[1] http://www.postgresql.org/message-id/56583BDD.9060302@2ndquadrant.com
It's a fairly simple patch, but obviously it touches very complex part
of the code. I'll add it to 2016-01 CF.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| xlog-last-known-segment-v1.patch | text/x-diff | 3.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-12-12 21:35:32 | Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY |
| Previous Message | Andreas Seltenreich | 2015-12-12 20:30:17 | Re: [sqlsmith] Failed to generate plan on lateral subqueries |