Re: Constraint documentation - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Constraint documentation
Date
Msg-id alpine.DEB.2.21.1807131030070.27883@lancre
Whole thread Raw
In response to Re: Constraint documentation  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hello Peter,

>> I'm not sure what is the suggestion wrt to the documentation text. Is the
>> issue only with the first introductory sentence? Would removing it be
>> enough?
>
> Yes.  But it would be even better to fix pg_dump.

Sure. The purpose of Lætitia patch is simply to document the consequences 
if the current behavior. Fixing pg_dump is another issue:-)

I guess that this would involve postponing all non trivial CHECK 
declarations to after all table and function creations. While waiting for 
such a significant change, ISTM that documenting the issue is a reasonable 
option.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots