Re: WIP fix proposal for bug #6123 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: WIP fix proposal for bug #6123
Date
Msg-id 4E37FFC4020000250003F9B9@gw.wicourts.gov
Whole thread Raw
In response to Re: WIP fix proposal for bug #6123  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote:
> Florian Pflug <fgp@phlo.org> wrote:
>> Hm, OK I see your point now I believe. This is not so much about
>> wanting to put things into BEFORe triggers which doesn't really
>> fit there, but instead avoiding weeks of debugging if someones
>> messes up.
>  
> I would say that is the overriding concern.
I'm going to have to argue with myself -- really, the *biggest*
concern is that the current situation allows data to be quietly
mangled through non-obvious action-at-a-distance.  The damage might
not be discovered for a very long time.  Debugging the cause of the
mangling, once noticed, is the *next* most significant concern.
-Kevin


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: WIP fix proposal for bug #6123
Next
From: Tom Lane
Date:
Subject: Transient plans versus the SPI API