Re: proposal : backend startup hook / after logon trigger

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tomas Vondra" <tv(at)fuzzy(dot)cz>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: proposal : backend startup hook / after logon trigger
Date: 2011-11-25 16:48:09
Message-ID: 11241.1322239689@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Tomas Vondra" <tv(at)fuzzy(dot)cz> writes:
> On 25 Listopad 2011, 2:44, Robert Haas wrote:
>> I've thought of this before, but I'm not exactly clear on what the use
>> cases are.

> The startup hook is useful for initializing an extension written in C,
> when the extension was loaded from postgresql.conf. If you need to perform
> the initialization for each db separately (so that you can decide whether
> to apply the extension to the user/database), you need to do that after
> the backend starts.

If you need that, just load the extension with local_preload_libraries.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-11-25 16:53:21 Re: proposal: use errcontext for custom exception too
Previous Message Dean Rasheed 2011-11-25 16:45:34 Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID