From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: System triggers |
Date: | 2003-05-16 17:56:55 |
Message-ID: | m3vfwabwrc.fsf@varsoon.wireboard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> writes:
> On Friday 16 May 2003 22:26, Doug McNaught wrote:
> > "Connection startup triggers" might be useful, and there's no good way
> > of doing them outside the database unless you wire it into every
> > client app, which kind of defeats the purpose...
>
> Umm.. As far as I know, if FE-BE protocol provides support for connection
> level triggers and libpq implements it, almost every client access library
> would get them automagically..
I don't see that the FE/BE protocol has anything to do with it. When
a new backend starts up, it would check pg_trigger for any connection
startup triggers and execute them--the client wouldn't know anything.
Of course, what happens to the output (if any) from those triggers,
given that the client probably doesn't expect it, is an interesting
question...
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Sailesh Krishnamurthy | 2003-05-16 18:01:48 | Re: System triggers |
Previous Message | Shridhar Daithankar | 2003-05-16 17:12:35 | Re: System triggers |