| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | Tom Dunstan *EXTERN* <pgsql(at)tomd(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposed feature: Selective Foreign Keys |
| Date: | 2013-12-02 10:06:40 |
| Message-ID: | 20131202100639.GB17643@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-12-02 08:57:01 +0000, Albe Laurenz wrote:
> What strikes me is that since foreign key constraints are implemented
> as triggers in PostgreSQL, this solution would probably not have many
> performance benefits over a self-written trigger that implements the
> same functionality. Since you need two triggers for your example,
> the performance might even be worse than a single self-written trigger.
Note that you cannot really write correct RI triggers without playing
very low level games, i.e. writing C and using special kinds of
snapshots and such.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-12-02 10:07:25 | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |
| Previous Message | Michael Paquier | 2013-12-02 09:45:37 | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |