Re: improve performance of pg_dump --binary-upgrade

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: improve performance of pg_dump --binary-upgrade
Date: 2024-04-18 20:33:08
Message-ID: 93129B02-33E0-4591-96B4-0B9C2183C7B4@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Apr 2024, at 22:28, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> On Thu, Apr 18, 2024 at 10:23:01AM -0500, Nathan Bossart wrote:
>> On Thu, Apr 18, 2024 at 09:24:53AM +0200, Daniel Gustafsson wrote:
>>> That does indeed seem like a saner approach. Since we look up the relkind we
>>> can also remove the is_index parameter to binary_upgrade_set_pg_class_oids
>>> since we already know that without the caller telling us?
>>
>> Yeah. It looks like that's been possible since commit 9a974cb, so I can
>> write a prerequisite patch for this.
>
> Here's a new patch set with this change.

From a read-through they look good, a very nice performance improvement in an
important path. I think it would be nice with some comments on the
BinaryUpgradeClassOids struct (since the code using it is thousands of lines
away), and a comment on the if (oids == NULL) block explaining the caching.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2024-04-18 20:51:31 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands
Previous Message Thomas Munro 2024-04-18 20:29:27 Re: Cannot find a working 64-bit integer type on Illumos