| From: | Andreas Zeugswetter <andreas(dot)zeugswetter(at)telecom(dot)at> |
|---|---|
| To: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgreSQL(dot)org> |
| Subject: | AW: [HACKERS] Dropping tables... |
| Date: | 1998-08-03 11:57:46 |
| Message-ID: | 01BDBEE7.54A08250@zeugswettera.user.lan.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vadim Mikheev wrote:
>
> Andreas Zeugswetter wrote:
> >
> > 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.
>
> Ok, currently, table can't be dropped if SELECTed by another
> running transaction.
>
> Would we like to change this ?!
No, I think this is ok. I thought the current behavior was that a selecter won't
do a lock, and therefore drop table would work and wanted to give an argument to leave it as is.
I regard a drop table to be seldom used, e.g. at product installations or upgrades.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vince Vielhaber | 1998-08-03 12:40:29 | Re: [HACKERS] indexes and floats |
| Previous Message | Maarten Boekhold | 1998-08-03 07:13:31 | Re: [HACKERS] TODO item: make pg_shadow updates more robust |