Postgres Pro
Downloads
Home   >   mailing lists

Re: Delete rule does not prevent truncate - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Delete rule does not prevent truncate
Date
Msg-id CANu8Fixq3_-OZgCHqrz_-tOfkm4EmL_Qq225D+grofVtW=MK-g@mail.gmail.com
Whole thread Raw
In response to Re: Delete rule does not prevent truncate  (Tim Smith <randomdev4@gmail.com>)
List pgsql-general
Tree view
For crying out loud GET OVER IT! You've been given a very reasonable and quick solution to your problem.
You can either
1. Keep crying and moaning until someone changes the rules.
2. Give up and port to another database.
3. Write the triggers and solve your problem!

On Fri, Jul 24, 2015 at 5:27 AM, Tim Smith <randomdev4@gmail.com> wrote:
On 23 July 2015 at 19:25, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> stick to triggers, they're faster


Erm, not according to your beloved manual !!!

38.7. Rules Versus Triggers

" a rule issuing one extra command is likely to be faster than a trigger"
"The summary is, rules will only be significantly slower than triggers
if their actions result in large and badly qualified joins, a
situation where the planner fails."


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Connections closing due to "terminating connection due to administrator command"
Next
From: Adrian Klaver
Date:
Subject: Re: Connections closing due to "terminating connection due to administrator command"