Horton

Re: foreign table creation and NOT VALID check constraints

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, Simon Riggs <simon@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-05T14:52:35Z
Lists: pgsql-hackers 
On Thu, Aug 3, 2017 at 9:29 PM, Amit Langote
<Langote_Amit_f8@lab.ntt.co.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

Commits

  1. Allow a foreign table CHECK constraint to be initially NOT VALID.

  2. Mark CHECK constraints declared NOT VALID valid if created with table.