Re: ALTER TABLE lock strength reduction patch is unsafe
От | Robert Haas |
---|---|
Тема | Re: ALTER TABLE lock strength reduction patch is unsafe |
Дата | |
Msg-id | BANLkTimeEd0xzO1tBC4EGqvs+0i82vrd2g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ALTER TABLE lock strength reduction patch is unsafe ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: ALTER TABLE lock strength reduction patch is
unsafe
|
Список | pgsql-hackers |
On Mon, Jun 20, 2011 at 9:42 AM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > Simon Riggs <simon@2ndQuadrant.com> wrote: > >> I'm looking for opinions ranging from fix-now-and-backpatch thru >> to ignore and discuss for 9.2. > > If it's a pre-existing bug I would think that one option would be to > put it into the next bug-fix release of each supported major release > in which it is manifest. Of course, if it is *safe* to work it into > 9.1, that'd be great. I'm currently on the other end of the spectrum: ignore and consider for 9.2. But that's mostly based on the belief that there isn't going to be a way of fixing this that isn't far too invasive to back-patch. Should that turn out to be incorrect, that's a different matter, of course... -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: