| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Lætitia Avrot <laetitia(dot)avrot(at)gmail(dot)com>, bpd0018(at)gmail(dot)com, vik(dot)fearing(at)2ndquadrant(dot)com, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Constraint documentation |
| Date: | 2018-07-13 08:39:53 |
| Message-ID: | alpine.DEB.2.21.1807131030070.27883@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2018-07-13 08:40:04 | Re: [HACKERS] Restricting maximum keep segments by repslots |
| Previous Message | Peter Eisentraut | 2018-07-13 08:22:21 | Re: file cloning in pg_upgrade and CREATE DATABASE |