| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | table vs domain constraints in ObjType |
| Date: | 2014-12-20 02:23:08 |
| Message-ID: | 20141220022308.GY1768@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Right now, both table and domain constraints share the same
classification in the ObjType enum, OBJECT_CONSTRAINT. For my patch to
implement improved object drop reporting in event triggers, it is
necessary to separate them, as per in the attach patch.
One emerging side-effect is that it is now possible to execute COMMENT
ON domain constraints, which wasn't previously possible. (I added \dd
support to psql as well.)
This is part of the patch for "replicating DROP commands across
servers",
http://archives.postgresql.org/message-id/20140826135459.GD6343@eldon.alvh.no-ip.org
which I just split up.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| domconstraint.patch | text/x-diff | 15.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2014-12-20 02:26:58 | Re: Reducing lock strength of adding foreign keys |
| Previous Message | David G Johnston | 2014-12-20 02:03:54 | Re: POLA violation with \c service= |