Re: Minor improvements in alter_table.sgml

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Minor improvements in alter_table.sgml
Date: 2014-04-08 16:23:34
Message-ID: CA+TgmoZtZ+SfCdezSbun7-DhbbE=EF6CDYCMTeTn2qQ9jtQ=uw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 8, 2014 at 5:05 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Attached is a patch to improve the manual page for the ALTER TABLE command.

Do we really need to add a section for "type_name" when we already
have a section for "OF type_name"?

constraint_name is also used for adding a constraint using an index.
So it could not only be a constraint to alter, validate, or drop, but
also a new constraint name to be added. Honestly, how much value is
there in even having a section for this? Do we really want to
document constraint_name as "name of an existing constraint, or the
name of a new constraint to be added"? It would be accurate, then,
but it also doesn't really tell you anything you didn't know already.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2014-04-08 16:27:08 Re: Problem with displaying "wide" tables in psql
Previous Message Andres Freund 2014-04-08 16:19:05 Re: Problem with displaying "wide" tables in psql