Re: Minor correction in alter_table.sgml - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Minor correction in alter_table.sgml
Date
Msg-id 19669.1480522630@sss.pgh.pa.us
Whole thread Raw
In response to Re: Minor correction in alter_table.sgml  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Minor correction in alter_table.sgml  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Re: [HACKERS] Minor correction in alter_table.sgml  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> Seems like this would be a bit better:

> ------
> All the actions, when acting on a single table and not using the ALL IN
> TABLESPACE form, except RENAME and SET SCHEMA, can be combined into a
> list of multiple alterations to be applied.
> ------

> I note that we say 'in parallel', but given that we have actual parallel
> operations now, we should probably shy away from using that except in
> cases where we actually mean operations utilizing multiple parallel
> processes.

I follow your beef with use of the word "parallel", but your proposed
rewording loses the entire point of multiple actions per ALTER TABLE;
namely that they're accomplished without repeated scans of the table.

Also the above seems a bit clunky; doesn't ALL IN TABLESPACE fall outside
the restriction "acting on a single table"?

So maybe something like
All the forms of ALTER TABLE that act on a single table,except RENAME and SET SCHEMA, can be combined into alist of
multiplealterations to be applied together.
 

We would have to enlarge on what "together" means, but I think there may
already be text explaining that further down.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Declarative partitioning - another take
Next
From: Christian Ullrich
Date:
Subject: Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013