Re: GUC failure on exception - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: GUC failure on exception
Date
Msg-id 4B7BE940.6000402@dunslane.net
Whole thread Raw
In response to Re: GUC failure on exception  (Tim Bunce <Tim.Bunce@pobox.com>)
List pgsql-hackers

Tim Bunce wrote:
> Did this ever get turned into a formal bug report with a number?
>   

No, and nobody seemed to care much about the poroblem :-( Maybe I will 
get a chance to do something about it during the next few weeks, 
although I am currently busier than a one legged man in a butt-kicking 
contest.

The GUC code is a mess w.r.t. this, and I didn't come up with a nice 
solution. Everything I thought of to try to fix it was so unspeakably 
ugly and fragile that I didn't even bother bringing it up.

The one thing we could possibly usefully do for plperl is to move the 
GUC setup code from _PG_init() to plperl_init_interp(), protected by a 
flag to make sure it only runs once. But most of the problem lies 
outside plperl's code.

But by all means file a bug report, so we don't lose track of it.

cheers

andrew



pgsql-hackers by date:

Previous
From: Tim Bunce
Date:
Subject: Re: GUC failure on exception
Next
From: Tom Lane
Date:
Subject: Re: Listen / Notify - what to do when the queue is full