From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nicolas Kowalski <Nicolas(dot)Kowalski(at)imag(dot)fr> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: VACUUM warning/error (?) |
Date: | 2001-01-18 18:08:17 |
Message-ID: | 3962.979841297@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Nicolas Kowalski <Nicolas(dot)Kowalski(at)imag(dot)fr> writes:
> NOTICE: FlushRelationBuffers(trace_sql, 162): block 239 is referenced
> (private
> 0, global 1)
> FATAL 1: VACUUM (vc_repair_frag): FlushRelationBuffers returned -2
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> connection to server was lost
> All seems to work, in particular this 'trace_sql' table, but what does
> mean this error message ?
It's complaining about a buffer reference count leakage --- most likely
due to the bug in 7.0.* whereby a backend may fail to run transaction-
abort code before shutting down, if the client disconnects in the middle
of a transaction block.
You could get rid of the immediate problem by restarting the postmaster,
but I recommend updating to 7.0.3 to fix the real bug.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-18 18:20:54 | Re: 7.1 initdb error |
Previous Message | Lamar Owen | 2001-01-18 18:00:34 | Re: row size limitation |