Re: Feedback on writing extensible modules - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Feedback on writing extensible modules
Date
Msg-id 20090601162322.GC5716@alvh.no-ip.org
Whole thread Raw
In response to Re: Feedback on writing extensible modules  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: Feedback on writing extensible modules  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Dimitri Fontaine wrote:

> Le 31 mai 09 à 18:21, Tom Lane a écrit :

>> You could maybe make this work by executing your own transaction
>> to do it, but I really have to wonder if it's a good idea.  One
>> point to think about is that elog(ERROR) still means elog(FATAL)
>> at this point, so any brokenness in the queries you're trying to
>> prepare will result in locking all users out of the database.
>
> Yeah that's a pretty good foot gun, yet another one. But  
> preprepare.at_init is optional and defaults to off. If you broke it all, 
> you can turn it off again and reload.

Maybe you could set a callback to be called during the first transaction
in InitPostgres ... in full knowledge that if it fails, people will be
locked out of the database.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Next
From: Tom Lane
Date:
Subject: It's June 1; do you know where your release is?