Re: Challenges preventing us moving to 64 bit transaction id (XID)?
От | Andres Freund |
---|---|
Тема | Re: Challenges preventing us moving to 64 bit transaction id (XID)? |
Дата | |
Msg-id | 20180301230712.nxg2u7nm4mtugprx@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Challenges preventing us moving to 64 bit transaction id (XID)? (Alexander Korotkov <a.korotkov@postgrespro.ru>) |
Ответы |
Re: Challenges preventing us moving to 64 bit transaction id (XID)?
|
Список | pgsql-hackers |
On 2018-03-02 01:56:00 +0300, Alexander Korotkov wrote: > On Fri, Mar 2, 2018 at 1:51 AM, Andres Freund <andres@anarazel.de> wrote: > > > On 2018-03-02 01:48:03 +0300, Alexander Korotkov wrote: > > > Also, the last commitfest is already too late for such big changes. > > > So, I'm marking this RWF. > > > > Agreed. Perhaps extract the 64bit GUC patch and track that separately? > > Seems like something we should just do... > > > > Sounds reasonable. But I didn't notice if there are other users for 64bit > GUCs besides 64bit xids? I think there were a couple past occasions where we could've used that, don't quite recall the details. We're at least not that far away from the point where various size limits are actually limited by int32 range. And timeouts of ~25 days are long but not entirely unreasonable. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: