Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, Nikita Malakhov <hukutoc(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value
Date: 2024-03-07 22:56:17
Message-ID: 20240307225617.GA615950@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 05, 2024 at 04:28:23PM +0900, Yugo NAGATA wrote:
> On Thu, 1 Feb 2024 17:59:56 +0800
> jian he <jian(dot)universality(at)gmail(dot)com> wrote:
>> v6 patch looks good.
>
> Thank you for your review and updating the status to RwC!

I think this one needs a (pretty trivial) rebase. I spent a few minutes
testing it out and looking at the code, and it seems generally reasonable
to me. Do you think it's worth adding something like a
pg_column_toast_num_chunks() function that returns the number of chunks for
the TOASTed value, too?

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2024-03-08 00:12:40 CREATE TABLE creates a composite type corresponding to the table row, which is and is not there
Previous Message Nathan Bossart 2024-03-07 22:00:47 Re: postgres_fdw test timeouts