From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: Vadim Mikheev <vadim@krasnet.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: RE: [HACKERS] DROP TABLE does not drop a table completely
Date: Mon, 17 May 1999 16:40:56 +0900
Message-ID: <000801bea038$993d59a0$2801007e@cadzone.tpf.co.jp> (raw)
In-Reply-To: <373FBEBF.C09E99B@krasnet.ru>
> -----Original Message-----
> From: root@sunpine.krs.ru [mailto:root@sunpine.krs.ru]On Behalf Of Vadim
> Mikheev
> Sent: Monday, May 17, 1999 4:01 PM
> To: Hiroshi Inoue
> Cc: pgsql-hackers
> Subject: Re: [HACKERS] DROP TABLE does not drop a table completely
>
>
> Hiroshi Inoue wrote:
> >
> > > >
> > > > ERROR: cannot open segment 1 of relation sessions_done_id_index
> > > >
> > >
> > > I got the same error in my test cases.
> > > I don't understand the cause of this error.
> > >
> >
> > I got this error message by dropping a table while concurrent
> transactions
> > inserting rows to the same table.
> >
> > I think other transactions should abort with message "Table does not
> > exist". But in most cases the result is not so.
> >
> > It seems that other transactions could proceed before DROP TABLE
> > command is completed.
> >
> > AFAIC heap_destroy_with_catalog() acquires AccessExclusiveLock and
> > releases the lock inside the function.
> >
> > I think that heap_destroy_with_catalog() (or upper level
> function) should
> > not
> > release the lock.
>
> You're right - this should be done keeping in mind that DROP is allowed
> inside BEGIN/END (long transactions), but I'm not sure that this
> will help generally: does it matter when unlock dropped relation -
> in heap_destroy_with_catalog() or in commit?
Unlocking dropped relation before commit enables other transactions
proceed and the transactions regard the relation as still alive before the
^^^^^^^^^
commit of DROP TABLE command(It's right,I think). As a result,those
transactions behave strangely,though I don't know more about the
reason.
Thanks.
Hiroshi Inoue
Inoue@tpf.co.jp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: Inoue@tpf.co.jp, vadim@krasnet.ru, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] DROP TABLE does not drop a table completely
In-Reply-To: <000801bea038$993d59a0$2801007e@cadzone.tpf.co.jp>
References: <373FBEBF.C09E99B@krasnet.ru> <000801bea038$993d59a0$2801007e@cadzone.tpf.co.jp>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox