| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | CREATE CONSTRAINT TRIGGER |
| Date: | 2010-11-05 21:37:05 |
| Message-ID: | 1288989935-sup-8185@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Some time ago, CREATE CONSTRAINT TRIGGER was a deprecated command and it
was slated for obsolence or removal.
Recent developments have turned it back into non-deprecated mode; it's
not going anywhere, and it needs to be fully documented.
It seems to me that it makes more sense to merge its documentation into
the CREATE TRIGGER page, where it belongs. Right now, the documentation
page for CREATE CONSTRAINT TRIGGER is 50% a repetition of what's in the
CREATE TRIGGER page; and a significant portion of the rest is spent
telling the user to refer to the CREATE TRIGGER page. The original
information to be found in CREATE CONSTRAINT TRIGGER is not all that
much.
Thus the attached patch.
--
Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fold-the-CREATE-CONSTRAINT-TRIGGER-doc-page-into-CRE.patch | application/octet-stream | 13.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-05 21:45:53 | "Make" versus effective stack limit in regression tests |
| Previous Message | Marti Raudsepp | 2010-11-05 21:09:48 | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |