Re: Avoid repeated PQfnumber() in pg_dump - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Avoid repeated PQfnumber() in pg_dump
Date
Msg-id BFCCF27A-59D1-40C5-A3B7-751A52762DE3@yesql.se
Whole thread Raw
In response to Avoid repeated PQfnumber() in pg_dump  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
Responses RE: Avoid repeated PQfnumber() in pg_dump  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
List pgsql-hackers
> On 14 Jul 2021, at 10:54, houzj.fnst@fujitsu.com wrote:

> Since PQfnumber() is not a cheap function, I think we'd better invoke
> PQfnumber() out of the loop like the attatched patch.

Looks good on a quick readthrough, and I didn't see any other similar codepaths
in pg_dump on top of what you've fixed.

> After applying this change, I can see about 8% performance gain in my test environment
> when dump table definitions which have many columns.

Out of curiosity, how many columns are "many columns"?

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Quick tip on building pg with Visual Studio Build Tools 2019 + small patches
Next
From: Tom Lane
Date:
Subject: Re: automatically generating node support functions