Horton

Re: Removing log_cnt from pg_sequence_read_tuple()

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-08-29T05:11:22Z
Lists: pgsql-hackers

Attachments

On Wed, Aug 28, 2024 at 08:28:03PM -0500, Nathan Bossart wrote:
> On Thu, Aug 29, 2024 at 08:00:52AM +0900, Michael Paquier wrote:
>> Indeed, pg_sequence_read_tuple() would not reflect the reality, some
>> ideas: 
>> - pg_sequence_read_data
>> - pg_sequence_get_data
>> - pg_sequence_data
>> - More consistent with other catalog functions: pg_get_sequence_data,
>> as we have already in the tree a lot of pg_get_* functions.
> 
> pg_get_sequence_data() sounds fine to me.

Okay, here is a v2 of the patch using this name for the function.
--
Michael

Commits

  1. Rename pg_sequence_read_tuple() to pg_get_sequence_data()