Re: ALTER TABLESPACE MOVE command tag tweak - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: ALTER TABLESPACE MOVE command tag tweak
Date
Msg-id 20140623223824.GC5032@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: ALTER TABLESPACE MOVE command tag tweak  (Stephen Frost <sfrost@snowman.net>)
Responses Re: ALTER TABLESPACE MOVE command tag tweak  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost wrote:

> Any further thoughts on this?  I haven't tried to go implement anything
> yet but I'm definitely concerned that we may run into a keyword issue
> with ALTER TABLE, but I don't really want to add 'TABLES' either.
> Anyone have any other suggestions or ideas?

I thought that the suggestion to use MOVE was the most appropriate.
However I also concur that re-using MOVE from its current cursor-related
meaning would be troublesome from several PoVs, so if there's a synonym
of MOVE that we can use, that'd probably be better.  I don't like ALTER
TABLES myself; and having an ALTER TABLE command that affects several
tables seems counterintuitive as well.

How about RELOCATE ALL [ TABLES | INDEXES | ... ] IN TABLESPACE foo TO bar
?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [COMMITTERS] pgsql: Do all-visible handling in lazy_vacuum_page() outside its critic
Next
From: Andres Freund
Date:
Subject: Re: idle_in_transaction_timeout