RE: vacuumdb failed

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgreSQL(dot)org>
Subject: RE: vacuumdb failed
Date: 2000-08-30 08:05:26
Message-ID: 000101c01259$0de86fe0$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -----Original Message-----
> From: Tom Lane
>
> > Now, I'm not sure if this is related, but while trying to
> do vacuumdb
> > <dbname>, I got...
>
> > NOTICE: FlushRelationBuffers(all_flows, 500237): block 171439 is
> > referenced (private 0, global 1)
> > FATAL 1: VACUUM (vc_repair_frag): FlushRelationBuffers returned -2
>
> Probably not related. We've seen sporadic reports of this error in 7.0,
> but it's been tough to get enough info to figure out the cause. If you
> can find a reproducible way to create the block-is-referenced condition
> we'd sure like to know about it!
>

The following is an example which doesn't release the reference count.
Neither CommitTransaction() nor AbortTransaction() is called after '\q'

begin;
declare myc cursor for select * from ..;
fetch in myc;
\q

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Davide G. Borin 2000-08-30 08:42:54 PostgreSQL slow on Reiserfs?
Previous Message Stephan Richter 2000-08-30 07:40:47 PL/pgSQL