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 |
---|---|
Тема | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Дата | |
Msg-id | 20130816174217.GB6147@eldon.alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: ALTER SYSTEM SET command to change postgresql.conf parameters
(RE: Proposal for Allow postgresql.conf values to be changed via
SQL [review])
Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
Список | pgsql-hackers |
Robert Haas escribió: > On Fri, Aug 9, 2013 at 8:44 AM, Stephen Frost <sfrost@snowman.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. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: