Re: Pgstattuple on Sequences: Seeking Community Feedback on Potential Patch

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pgstattuple on Sequences: Seeking Community Feedback on Potential Patch
Date: 2024-09-13 03:41:27
Message-ID: ZuO0Z4fjTrmgCm4-@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 12, 2024 at 10:40:11PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
>> Here's a patch to make the sequence permanent and to make the output of
>> tuple_data_split() not depend on endianness.
>
> +1 --- I checked this on mamba's host and it does produce
> "\\x0100000000000001" regardless of endianness.

Thanks for checking. I'll commit this fix in the morning.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2024-09-13 04:03:13 Re: Switch PgStat_HashKey.objoid from Oid to uint64
Previous Message Laurenz Albe 2024-09-13 02:41:40 Re: Mutable foreign key constraints