On Mon, 2007-04-23 at 17:38 -0400, Tom Lane wrote:
> I'm really still opposed to the entire concept. You're proposing to put
> a lot of fragile-looking code into a seldom-exercised error path.
There's certainly not a "lot" of code: the patch just adds a few
syscache lookups, wrapped in a PG_LOCK_NOWAIT() block.
As for fragility, I think the important point is whether it's safe to
siglongjmp() out of LockAcquire(); the rest is just window dressing.
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2007-04-23 22:11:29|
|Subject: Re: Better error message for select_common_type()|
|Previous:||From: Andrew Dunstan||Date: 2007-04-23 22:05:19|
|Subject: Re: RETURN QUERY in PL/PgSQL?|