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 16:56:39 |
Message-ID: | m38yt6de48.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:
> Hi,
>
> I was going thr. a oracle refresher course today. I came across this concept
> of system triggers which can be installed on things like database/connection
> startup.
>
> I think it would be a good addition to psotgresql. I was planning to hack
> dblink for multiple named persistent connections. ( HI Joe, I am still
> here..:-))) In that case, it would be a very easy thing to do to open a
> remote database connection whenever a new connection is opened to database.
> This way remote database would be totally transparent to end user..
IMHO, and I'm not a core developer, there's no need for "database
startup triggers"--whatever process starts the database can run an SQL
script at that time.
"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...
> Can this be taken for future versions?
I'm sure your patches would be considered for inclusion. :)
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-05-16 17:12:31 | Re: Static snapshot data |
Previous Message | Ricardo Ryoiti S. Junior | 2003-05-16 16:43:04 | Re: [Fwd: [HACKERS] Heads up: 7.3.3 this Wednesday] |