Re: AW: Issue NOTICE for attempt to raise lock level? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: AW: Issue NOTICE for attempt to raise lock level?
Date
Msg-id 14873.973626069@sss.pgh.pa.us
Whole thread Raw
In response to RE: AW: Issue NOTICE for attempt to raise lock level?  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
Responses Re: AW: Issue NOTICE for attempt to raise lock level?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
> BTW, what about indices?

CREATE/DROP INDEX grab exclusive lock on the parent table, so there's no
problem with indexes as long as transactions that use the parent table
hold some kind of lock on that table.  I figure it's OK for the executor
to continue to grab and release locks on indexes on a per-scan basis.
It's just the parent table that we need a continuous lock on.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: AW: AW: Issue NOTICE for attempt to raise lock leve l?
Next
From: Tom Lane
Date:
Subject: Re: AW: Issue NOTICE for attempt to raise lock level?