On 2015-09-11 14:25:39 +0200, Christoph Berg wrote: > A few more words here: the archive recovery was a pitr to 00:45, so > well before the problem, and the cluster was initially working well, > but crashed shortly after with the same mxid 1068235595 message. The > crash was triggered from a delete on a different table (which was > related schema-wise, but iirc neither of these tables has any FKs). > > We then rewound the system to a zfs snapshot taken when the archive > recovery had finished (db shut down cleanly), and put it up again, > when it again crashed with mxid 1068235595, this time on a third > table. > > The original crash and the first post-recovery crash happened a few > minutes after pg_start_backup(), though the next crash was without > that.
Do you still have access to that data? That'd make investigation of both the issue and fixes/workaround far easier. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
