Stuart Bishop <stu...@stuartbishop.net> writes:
> I just had a brief outage on a production server running 8.3.6, which
> I suspect was triggered by me running a table bloat report making lots
> of pgstattuple calls.
> The first I got of it was the script I'd just kicked off died:
> could not open segment 1 of relation 1663/16409/11088101 (target block
> 131292): No such file or directory
> CONTEXT: writing block 131292 of relation 1663/16409/11088101
> ...
> Doing an immediate shutdown and restart seems to have brought
> everything back online.
What's the actual size of that relation now? Is it growing rapidly?
(I'm trying to figure out whether those writes *should* have succeeded,
or whether the block numbers were corrupt in memory.)
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
