Re: Tom Lane 2012-07-02 <18088.1341245035@sss.pgh.pa.us>
> Christoph Berg <christoph.berg@credativ.de> writes:
> > What is still puzzling me is that the customer is repeatedly reporting
> > these issues, even after rebooting the system.
>
> Hm. A server restart really ought to clear any problem in this area,
> since pg_notify gets reset to starting conditions. Please check into
> that more closely. (It might be worth looking at $PGDATA/pg_notify/
> after a restart just to verify there are no files there except 0000.)
Hi,
we deployed an updated 9.1.4 package with your patch there. After
restarting the server, pg_notify was empty except for 0000. fsck.ext3
reported no errors.
Now the error has happened again, 58P01, could not read status of
transaction 0, could not open pg_notify/0016, ENOENT, location
SlruReportIOError, slru.c:840. (Roughly translated from the German
message.)
We'll try to dig into the code here, maybe we can spot something.
Mit freundlichen Grüßen,
Christoph Berg
--
Tel.: +49 (0)21 61 / 46 43-187
credativ GmbH, HRB Mönchengladbach 12080
Hohenzollernstr. 133, 41061 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz