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

* Alvaro Herrera (alvherre(at)2ndquadrant(dot)com) wrote:
> Robert Haas escribió:
> > On Fri, Aug 9, 2013 at 8:44 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > > 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.
> >
> > Eh, maybe. I'm not sure there's enough use case for that to justify
> > the amount of infrastructure it would require. I'm happy with the
> > recent enhancements to background workers, but there's an awful lot of
> > ground to cover between that and what you're proposing.
>
> Yeah, agreed. There's a lot of infrastructure required for this; it
> seems hard to justify it only to support disabling ALTER SYSTEM.

This would be support for generic triggers on shared catalog updates,
which would certainly extend beyond just ALTER SYSTEM and into ALTER
DATABASE and ALTER ROLE..

Thanks,

Stephen