On Fri, Aug 09, 2013 at 03:08:45PM +0200, Dimitri Fontaine wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > A shared catalog which defined which *database* to run the trigger
> > in, with a way to fire off a new backend worker in that database
> > and tell it to run the trigger, might be interesting and would
> > deal with the issue that the trigger would behave differently
> > depending on the database connected to. That would bring along
> > other issues, of course, but it seemed an interesting enough idea
> > to mention.
>
> Yeah, I like that approach. The only drawback is that it requires
> having PLproxy in core first, or something like Foreign Functions or
> something.
SQL/MED does define such an API. Whether we find it useful enough to
make it the default way of doing things is a separate matter. I'll do
some research.
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
