Is it possible to have a FATAL error that crashes a backend and for it to *not* have written an abort WAL record for any previously active transaction?
I think yes, but haven't managed to create this situation while testing for it. If we either *always* write a WAL record, or PANIC then that makes some coding easier, so seems sensible to check. -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
