Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: 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 13:08:45
Message-ID: m2iozft3j6.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-08-09 13:12:03 Re: CREATE EVENT TRIGGER syntax
Previous Message Robert Haas 2013-08-09 13:05:51 Re: mvcc catalo gsnapshots and TopTransactionContext