Quick Links

Re: Question about ALTER TABLE SET TABLESPACE locing behaviour

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	Hannu Krosing <hannu(at)skype(dot)net>
Cc:	PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: Question about ALTER TABLE SET TABLESPACE locing behaviour
Date:	2006-02-01 23:08:49
Message-ID:	6314.1138835329@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Hannu Krosing <hannu(at)skype(dot)net> writes:
> Does ALTER TABLE SET TABLESPACE lock the table

It had better ... see nearby discussion about relaxing locking for
TRUNCATE. Exactly the same problem that at commit we'd be cutting
the ground out from under any concurrent query.

regards, tom lane

In response to

Question about ALTER TABLE SET TABLESPACE locing behaviour at 2006-02-01 21:44:59 from Hannu Krosing

Responses

Re: Question about ALTER TABLE SET TABLESPACE locing at 2006-02-02 12:26:47 from Hannu Krosing

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Christopher Kings-Lynne	2006-02-02 01:15:59	8.1.3?
Previous Message	Hannu Krosing	2006-02-01 21:44:59	Question about ALTER TABLE SET TABLESPACE locing behaviour