Re: recovering from "found xmin ... from before relfrozenxid ..."
От | Robert Haas |
---|---|
Тема | Re: recovering from "found xmin ... from before relfrozenxid ..." |
Дата | |
Msg-id | CA+Tgmoab8xZeiy=K=eB3CYk0xy3pZSZrSKgDKDBYPh3EKSeQVA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: recovering from "found xmin ... from before relfrozenxid ..." (Fujii Masao <masao.fujii@oss.nttdata.com>) |
Список | pgsql-hackers |
On Mon, Jul 13, 2020 at 9:29 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: > But updating this tool can fit to the release schedule and > policy of PostgreSQL? > > While investigating the problem by using this tool, we may want to > add new feature into the tool because it's necessary for the investigation. > But users would need to wait for next minor version release, to use this > new feature. Yeah, that's a point that needs careful thought. I don't think it means that we shouldn't have something in core; after all, this is a problem that is created in part by the way that PostgreSQL itself works, and I think it would be quite unfriendly if we refused to do anything about that in the core distribution. On the other hand, it might be a good reason not to back-patch, which is something most people don't seem enthusiastic about anyway. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: