Re: Use pg_current_xact_id() instead of deprecated txid_current()
| От | Tom Lane |
|---|---|
| Тема | Re: Use pg_current_xact_id() instead of deprecated txid_current() |
| Дата | |
| Msg-id | 2645118.1770567884@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Use pg_current_xact_id() instead of deprecated txid_current() (Álvaro Herrera <alvherre@kurilemu.de>) |
| Ответы |
Re: Use pg_current_xact_id() instead of deprecated txid_current()
|
| Список | pgsql-hackers |
=?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de> writes:
> On 2026-02-08, Shinya Kato wrote:
>> Since pg_current_xact_id() returns xid8 which does not support
>> arithmetic operators, places that need "xid + 1" cast the result via
>> ::text::bigint first.
> I think it may be better to add some operators, or was there a rationale for these not being there?
I'm fairly concerned about overloading the arithmetic operators with
unsigned versions. The reason we never invented SQL-level uint8 and
such is fear of getting a lot of "ambiguous operator" errors. Now,
if we are careful not to create implicit casts between xid[8] and
any ordinary type, maybe it'd be okay to invent xid+int, xid8-int,
and a few more.
As things stand, I don't find the proposed patch to be an improvement.
regards, tom lane
В списке pgsql-hackers по дате отправления: