Re: Should we add xid_current() or a int8->xid cast?

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Should we add xid_current() or a int8->xid cast?
Дата
Msg-id 20200402180109.ihwozk3h7gcopw7g@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Should we add xid_current() or a int8->xid cast?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: Should we add xid_current() or a int8->xid cast?
Re: Should we add xid_current() or a int8->xid cast?
Список pgsql-hackers
Hi,

On 2020-04-02 14:33:18 -0300, Alvaro Herrera wrote:
> On 2020-Apr-02, Thomas Munro wrote:
> 
> > On Sat, Mar 21, 2020 at 11:14 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> > > * updated OIDs to avoid collisions
> > > * added btequalimage to btree/xid8_ops
> > 
> > Here's the version I'm planning to commit tomorrow, if no one objects.  Changes:
> > 
> > * txid.c renamed to xid8funcs.c
> > * remaining traces of "txid" replaced various internal identifiers
> > * s/backwards compatible/backward compatible/ in funcs.sgml (en_GB -> en_US)
> 
> Hmm, for some reason I had it in my head that we would make these use an
> "epoch/val" output format rather than raw uint64 values.

Why would we do that? IMO the goal should be to reduce awareness of the
32bitness of normal xids from as many places as possible, and treat them
as an internal space optimization.

Greetings,

Andres Freund



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Proposal: Expose oldest xmin as SQL function for monitoring
Следующее
От: David Zhang
Дата:
Сообщение: Re: Allow continuations in "pg_hba.conf" files