| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pgstattuple triggered checkpoint failure and database outage? |
| Date: | 2009-03-31 01:59:32 |
| Message-ID: | 28154.1238464772@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Stuart Bishop <stuart(at)stuartbishop(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-31 02:18:06 | Re: running two servers on one machine |
| Previous Message | Ow Mun Heng | 2009-03-31 01:20:59 | partial TEXT search on an index |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-03-31 02:55:24 | Re: Solaris getopt_long and PostgreSQL |
| Previous Message | Tom Lane | 2009-03-31 01:48:53 | Re: PQinitSSL broken in some use casesf |