Re: [HACKERS] Vacuum analyze bug CAUGHT

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: Michael Simms <grim(at)argh(dot)demon(dot)co(dot)uk>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Vacuum analyze bug CAUGHT
Date: 1999-09-10 06:49:58
Message-ID: 37D8AA16.8F767392@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hiroshi Inoue wrote:
>
> > crashtest=> vacuum analyze;
> > NOTICE: Rel pg_type: TID 4/3: InsertTransactionInProgress 129915
> > - can't shrink relation
...
>
> CREATE TABLE doesn't lock system tables till end of transaction.
> It's a cause of these NOTICE messages.
>
> Should we lock system tables till end of transaction ?

No, if we allow DDL statements inside BEGIN/END
(in long transaction).

> Moreover CREATE TABLE doesn't acquire any lock for pg_attribute
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> while tuples are inserted into pg_attribute.
> Concurrent vacuum may corrupt pg_attribute.

Should be fixed!

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 1999-09-10 09:19:45 RE: [HACKERS] Vacuum analyze bug CAUGHT
Previous Message Hiroshi Inoue 1999-09-10 06:42:53 RE: [HACKERS] Vacuum analyze bug CAUGHT