Tom Lane wrote:
Peter Eisentraut <[EMAIL PROTECTED]> writes:
PL/sh is OK, but both PL/Ruby and PL/Java play around with Warn_restart.
Are they using it to fake try/catch behavior? If so, see later thread
about moving to a simple set of try/catch macros.
I currently have this up and seemi
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> PL/sh is OK, but both PL/Ruby and PL/Java play around with Warn_restart.
Are they using it to fake try/catch behavior? If so, see later thread
about moving to a simple set of try/catch macros.
I currently have this up and seemingly working for the
Am Sonntag, 25. Juli 2004 01:48 schrieb Tom Lane:
> One issue is that it may break existing PLs that override Warn_restart,
> since the semantics of doing that will have changed a bit. We can
> easily fix the PLs that are in our own CVS, but what are the
> implications for other PLs such as PL/R a
Tom Lane wrote:
One issue is that it may break existing PLs that override Warn_restart,
since the semantics of doing that will have changed a bit. We can
easily fix the PLs that are in our own CVS, but what are the
implications for other PLs such as PL/R and PL/SH? Joe, Peter, any
comments?
I am
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yes. This is an integral part of finishing nested transactions.
> Oh, is this exceptions in functions or the ability to allow functions to
> keep executing after an SQL error?
Those are the same thing, aren't they? But yes, that's t
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Are you suggesting these changes for 7.5?
Yes. This is an integral part of finishing nested transactions.
regards, tom lane
---(end of broadcast)---
TIP 1: subscribe and unsubscri
Currently, the way that ereport/elog processing works is:
1. Collect up all the error parameter information into an ErrorData
structure. (This is somewhat nontrivial in itself, at least in the
ereport case, but I'll gloss over that here.)
2. Construct a log message and/or a client Error or Notic
