Pius Chan <pc...@contigo.com> writes: > The ERROR happened again. After several days of investigation and testing, I > can now reproduce the ERROR in my testing environment. The reason why the > ERROR used to happen in a certain time period is that our report batch jobs > run in that period and the batch job can make the TOAST area grow. I can > repeat the ERROR with this set up and testing procedure.
Thanks. It would've been easier if you'd provided a more concrete test procedure, but I've been able to reproduce what seems to be the same failure. I don't know exactly what to do about it yet :-( --- see http://www.postgresql.org/message-id/20362.1359747...@sss.pgh.pa.us At the moment it appears to me that this error could only occur in CLUSTER or its close cousin VACUUM FULL; ordinary database queries could not see such a failure. Does that agree with your experience? If so, this isn't really a data loss bug, so you should be able to just live with it until we can work out a fix. 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
