Re: Proposal for internal Numeric to Uint64 conversion function.

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Amul Sul <sulamul(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal for internal Numeric to Uint64 conversion function.
Date: 2022-02-16 11:20:54
Message-ID: 27eb25b4-aed3-b877-79a4-f940fc72ef6d@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16.02.22 06:00, Amul Sul wrote:
> Currently, numeric_pg_lsn is the only one that accepts the Numeric
> value and converts to uint64 and that is the reason all the type
> conversion code is embedded into it.

There are other functions such as numeric_int8() that work similarly.
If you are going to refactor, then they should all be treated similarly.
I'm not sure if it's going to end up being beneficial.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-02-16 11:26:53 Re: Fix a comment in worker.c
Previous Message osumi.takamichi@fujitsu.com 2022-02-16 11:19:06 RE: Optionally automatically disable logical replication subscriptions on error