Re: Trigger to run @ connection time?

On Thu, Mar 13, 2008 at 2:18 PM, Marko Kreen <markokr@gmail.com> wrote:
> On 3/13/08, Dawid Kuroczko <qnex42@gmail.com> wrote:
>  >  An application which uses tsearch2 ('SELECT set_curdict() / set_curcfg()' being
>  >  called upon session start).  That is fine and that works.
>  >
>  >  Now, using statement pooling solution like pgbouncer is great benefit for this
>  >  specific application.  There is one little problem however -- one can never be
>  >  sure when session is started.  As a countermeasure there is a need to call
>  >  set_curdict() in every transaction (which is very fast), but one needs
>  >  to remember
>  >  to call that set_curdict() every time.
>  >
>  >  ON CONNECT trigger would solve that neatly!
>
>  Hm.  It seems to make more sense to implement connect-time
>  hook directly in pgbouncer.

Indeed that would solve the issue.  But then again it could be argued that
PL/pgSQL could be implemented outside the backend as well. ;-)

I see it as an addition which does have its applications.

   Regards,
       Dawid