I wrote:
> ... Never mind that complaint then.
Be advised that I'm going to be on the warpath again in the morning.
I observe that the substantial amount of care we have taken over
XLogFlush's handling of bad-input-LSN scenarios has been completely
destroyed by the UpdateMinRecoveryPoint patch, which will fail
disastrously (leaving the database unstartable/unrecoverable) if a
bogusly large LSN is encountered during recovery.
However, I grow weary...
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
