aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-08-30 08:49:24 +0900
committerMichael Paquier <michael@paquier.xyz>2024-08-30 08:49:24 +0900
commita83a944e9fdd573802c82d961126ba07bfb65f98 (patch)
tree0d72e09dd3d9acc8b40537b064da18d49d787b00 /src/backend/access/gist/gistxlog.c
parent43f2e7634d838b39fd3fa3aaddb6964392d98312 (diff)
downloadpostgresql-a83a944e9fdd573802c82d961126ba07bfb65f98.tar.gz
postgresql-a83a944e9fdd573802c82d961126ba07bfb65f98.zip
Rename pg_sequence_read_tuple() to pg_get_sequence_data()
This commit removes log_cnt from the tuple returned by the SQL function. This field is an internal counter that tracks when a WAL record should be generated for a sequence, and it is reset each time the sequence is restored or recovered. It is not necessary to rebuild the sequence DDL commands for pg_dump and pg_upgrade where this function is used. The field can still be queried with a scan of the "table" created under-the-hood for a sequence. Issue noticed while hacking on a feature that can rely on this new function rather than pg_sequence_last_value(), aimed at making sequence computation more easily pluggable. Bump catalog version. Reviewed-by: Nathan Bossart Discussion: https://postgr.es/m/Zsvka3r-y2ZoXAdH@paquier.xyz
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions