| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | ALTER TABLE documentation |
| Date: | 2010-02-22 14:46:36 |
| Message-ID: | 603c8f071002220646w835ec85k42b39a1e1dbbbb3f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I just noticed that the current ALTER TABLE documentation doesn't do a
very good job differentiating between commands that affect the whole
table and commands that only affect specific columns.
http://developer.postgresql.org/pgdocs/postgres/sql-altertable.html
That didn't matter as much before, but now that we have both
table-level options and attribute-level options, there are two
sections in there that look all-too-similar... suggestions?
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-22 14:53:59 | Re: Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
| Previous Message | Alvaro Herrera | 2010-02-22 14:42:08 | Re: Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries |