Re: Lazy xid assignment V3
| От | Marko Kreen |
|---|---|
| Тема | Re: Lazy xid assignment V3 |
| Дата | |
| Msg-id | e51f66da0709030553k4dd476b0xe68714a7195352e4@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Lazy xid assignment V3 (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: Lazy xid assignment V3
|
| Список | pgsql-patches |
On 9/3/07, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Florian G. Pflug wrote: > > Since we didn't really reach an agreement on how xid_age should behave, > > I've reverted it back to the original version. So with this patch, > > xid_age will just force assignment of a xid. > > Is this really a good idea? I'm repeating myself, but a query like > > select age(xmin) from bigtable > > could accelerate Xid wraparound. If the server is running close to the > limit it could cause a shutdown to prevent the actual wraparound. Such query would take only one xid, which should not be a problem? -- marko
В списке pgsql-patches по дате отправления: