diff options
| author | Stephen Frost <sfrost@snowman.net> | 2016-12-21 15:03:37 -0500 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2016-12-21 15:03:37 -0500 |
| commit | eaac6c75858b693ef5e8968b509114c30896ba19 (patch) | |
| tree | 95bbbfe4507511e370bd24b68e30948d8ce2c8ce /src/backend/executor/nodeSamplescan.c | |
| parent | 542975a147525caa659ac08220b81c32a60f0a5c (diff) | |
| download | postgresql-eaac6c75858b693ef5e8968b509114c30896ba19.tar.gz postgresql-eaac6c75858b693ef5e8968b509114c30896ba19.zip | |
Improve ALTER TABLE documentation
The ALTER TABLE documentation wasn't terribly clear when it came to
which commands could be combined together and what it meant when they
were.
In particular, SET TABLESPACE *can* be combined with other commands,
when it's operating against a single table, but not when multiple tables
are being moved with ALL IN TABLESPACE. Further, the actions are
applied together but not really in 'parallel', at least today.
Pointed out by: Amit Langote
Improved wording from Tom.
Back-patch to 9.4, where the ALL IN TABLESPACE option was added.
Discussion: https://www.postgresql.org/message-id/14c535b4-13ef-0590-1b98-76af355a0763%40lab.ntt.co.jp
Diffstat (limited to 'src/backend/executor/nodeSamplescan.c')
0 files changed, 0 insertions, 0 deletions