From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Date: | 2013-08-09 14:58:16 |
Message-ID: | 20130809145816.GC9447@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Aug 09, 2013 at 03:08:45PM +0200, Dimitri Fontaine wrote:
> Stephen Frost <sfrost(at)snowman(dot)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(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-08-09 15:06:15 | Re: BUG #8335: trim() un-document behaviour |
Previous Message | Tom Lane | 2013-08-09 14:35:32 | Re: Proposal for XML Schema Validation |