Re: [COMMITTERS] pgsql: Add ALTER TABLESPACE ... MOVE command

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Add ALTER TABLESPACE ... MOVE command
Date: 2014-04-03 21:10:46
Message-ID: 11514.1396559446@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Stephen Frost wrote:
>> Add ALTER TABLESPACE ... MOVE command

> I just noticed that this commit added the new commands under the
> "ALTER THING name RENAME TO" production (which were originally for
> RenameStmt); since commit d86d51a95 had already added some
> AlterTableSpaceOptionsStmt nodes to the possible results, maybe this
> wasn't so bad in itself; but still it seems quite unlike the way we
> organize our parse productions.

Ick. That's just plain sloppy. Please create a separate production,
*and* a separate comment header.

Commit d86d51a95 was pretty damn awful in this regard as well, but
let's clean them both up, not make it worse.

Existing precedent would suggest inventing two new productions named the
same as the parse node types they produce, viz AlterTableSpaceMoveStmt
and AlterTableSpaceOptionsStmt.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2014-04-04 02:02:55 pgsql: Fix non-equivalence of VARIADIC and non-VARIADIC function call f
Previous Message Tom Lane 2014-04-03 20:57:58 pgsql: Code review for commit d26888bc4d1e539a82f21382b0000fe5bbf889d9.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-04-03 22:28:34 Re: WAL format and API changes (9.5)
Previous Message Alexander Korotkov 2014-04-03 19:44:03 Re: GSoC 2014 proposal