| From: | Andreas Zeugswetter <andreas(dot)zeugswetter(at)telecom(dot)at> |
|---|---|
| To: | "'vadim(at)krs(dot)ru'" <vadim(at)krs(dot)ru> |
| Cc: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org> |
| Subject: | |
| Date: | 1998-07-31 08:06:07 |
| Message-ID: | 01BDBC6B.7340C8B0@zeugswettera.user.lan.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vadim, bright as always wrote:
> ....
>9. ObjExclusiveLock - acquired by DROP/ALTER.
>
>: SELECT doesn't aquire any type of lock except of
> AccessSharedLock but this is short-term lock and would we
> like disallow DROP TABLE that was read by some running
> transaction ?
I would say allow the drop table, of course only if no update or intent update (select for update)
lock is on it. This is how Informix behaves. Otherwise it will become very hard to drop tables altogether.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Zeugswetter | 1998-07-31 08:51:43 | AW: [HACKERS] OR clause status report |
| Previous Message | Vadim Mikheev | 1998-07-31 05:46:25 | Re: [HACKERS] OR clause status report |