From: Hiroshi Inoue <Inoue@tpf.co.jp>
To: pgsql-hackers <pgsql-hackers@postgreSQL.org>
Subject: DROP TABLE does not drop a table completely
Date: Mon, 17 May 1999 11:30:45 +0900
Message-ID: <000a01bea00d$443b2b60$2801007e@cadzone.tpf.co.jp> (raw)
In-Reply-To: <000301be9d2b$638ea580$2801007e@cadzone.tpf.co.jp>
Hi all,
This mail is about the original cause of [HACKERS] spinlock freeze ?(Re:
INSERT/UPDATE waiting (another example)).
> -----Original Message-----
> From: owner-pgsql-hackers@postgreSQL.org
> [mailto:owner-pgsql-hackers@postgreSQL.org]On Behalf Of Hiroshi Inoue
> Sent: Thursday, May 13, 1999 7:29 PM
> To: Tom Lane; Wayne Piekarski
> Cc: pgsql-hackers@postgreSQL.org
> Subject: [HACKERS] spinlock freeze ?(Re: INSERT/UPDATE waiting (another
> example))
>
>
[snip]
> >
> > Then another one after restarting everything:
> >
> > 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.
Comments ?
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, pgsql-hackers@postgreSQL.org
Subject: Re: DROP TABLE does not drop a table completely
In-Reply-To: <000a01bea00d$443b2b60$2801007e@cadzone.tpf.co.jp>
References: <000301be9d2b$638ea580$2801007e@cadzone.tpf.co.jp> <000a01bea00d$443b2b60$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