| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: foreign table creation and NOT VALID check constraints |
| Date: | 2017-08-05 14:52:35 |
| Message-ID: | CA+Tgmob_i2Dv6Uo1UZC5vRHbK20qcRvhFYHjDGMVoCgK5MN-mQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 3, 2017 at 9:29 PM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Thanks for committing the code changes.
>
> About the documentation changes, it seems that the only places where any
> description of NOT VALID appears is ALTER TABLE, ALTER FOREIGN TABLE, and
> ALTER DOMAIN references pages. Even if the CREATE (FOREIGN) TABLE syntax
> allows it, NOT VALID does not appear in the syntax synopsis, so it seems
> kind of a hidden feature. Maybe, we should fix that first (if at all).
Yeah. If somebody wants to do a general survey of how NOT VALID is
documented and improve that, cool.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2017-08-05 15:36:03 | git.postgresql.org (and other services) down |
| Previous Message | Robert Haas | 2017-08-05 14:51:24 | Re: pg_stop_backup(wait_for_archive := true) on standby server |