Re: init script or procedure

2011/8/24 Merlin Moncure <mmoncure(at)gmail(dot)com>:
> On Wed, Aug 24, 2011 at 9:51 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> 2011/8/24 Merlin Moncure <mmoncure(at)gmail(dot)com>:
>>> On Wed, Aug 24, 2011 at 9:30 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>>> Hello
>>>>
>>>> 2011/8/24 Gauthier, Dave <dave(dot)gauthier(at)intel(dot)com>:
>>>>> Does PG support the use of an init script or procedure?  I'm looking for
>>>>> something that'll run unconditionally every time someone makes a DB
>>>>> connection.  This script will create a temp table and stuff some data in it
>>>>> for general use within that session.
>>>>>
>>>>
>>>> no, there is nothing similar. You have to call a own procedure after
>>>> login explicitly
>>>
>>> We could really use this.   It's kinda sorta possible to script SQL on
>>> connection close via C hook through dblink but not on session startup.
>>> It's not always possible for the client know when a backend session is
>>> fired up -- for example in connection pools.
>
> [snip]
>> . This is not task for server,
>
> I disagree.  Other databases have them (see
> http://msdn.microsoft.com/en-us/library/bb326598.aspx) and they are
> highly used and useful.

other databases has own integrated connection pooling

I am not absolutely against - but we need a integrated pool before

Pavel

>
> merlin
>