Re: Fwd: Successful post to pgsql-hackers
От | Alvaro Herrera |
---|---|
Тема | Re: Fwd: Successful post to pgsql-hackers |
Дата | |
Msg-id | 20130211134441.GA4737@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Fwd: Successful post to pgsql-hackers (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: Fwd: Successful post to pgsql-hackers
|
Список | pgsql-hackers |
Magnus Hagander escribió: > On Mon, Feb 11, 2013 at 5:01 AM, Alvaro Herrera > <alvherre@2ndquadrant.com> wrote: > > Magnus Hagander escribió: > >> On Sun, Feb 10, 2013 at 3:25 AM, Alvaro Herrera > >> <alvherre@2ndquadrant.com> wrote: > > > >> > I changed the defaults for new subscribers, and also the flags values > >> > for all existing subscribers, note. > >> > >> For *all* existing subscribers, or those that had not changed their > >> defaults? And did you change just those flags, or for all flags? > > > > For all existing subscribers, I changed the ackpost (to off), ackreject > > (to on), ackstall (to on) flags. Other flags were untouched. There's > > no way to distinguish "unchanged" from "set to the same as the default" > > in mj2, I'm afraid. > > Yeah, it seems you at least broke some cronjobs that relied on the old > default... Huh? We had cronjobs that relied on ackpost being set? Please elaborate. > That said, I think that was pretty darn unfriendly to those who > potentially changed their own configuration. E.g. all those who > potentially set their ackpost to on intentionally years ago, have now > lost that one... But it's clearly too late to do anything about that > one now. Yes, that true. Sorry about that. As I said, there was no way to figure that out. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: