Re: improve performance of pg_dump with many sequences - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: improve performance of pg_dump with many sequences
Date
Msg-id d7f5942e-00ba-4d90-9bac-f0b2b7092dc4@app.fastmail.com
Whole thread Raw
In response to Re: improve performance of pg_dump with many sequences  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: improve performance of pg_dump with many sequences
List pgsql-hackers
On Wed, Jul 10, 2024, at 7:05 PM, Nathan Bossart wrote:
I'm not following why that would be a better approach.  strncpy() will add
a NUL to the end of the string unless it doesn't fit in the buffer, in
which case we'll add our own via "seqtype[sizeof(seqtype) - 1] = '\0'".
Furthermore, the compiler can determine the position where the NUL should
be placed, whereas placing it at the end of the copied string requires a
runtime strlen().

Nevermind, you are copying the whole buffer (n = sizeof(seqtype)).

Unfortunately, I think we have to keep this workaround since older minor
releases of PostgreSQL don't have the fix.

Hmm. Right.

What pg_dump command did you test here?  Did you dump the sequence data, or
was this --schema-only?

time pg_dump -f - -s -d postgres


--
Euler Taveira

pgsql-hackers by date:

Previous
From: "Zhijie Hou (Fujitsu)"
Date:
Subject: RE: Conflict detection and logging in logical replication
Next
From: Yugo NAGATA
Date:
Subject: Re: Incremental View Maintenance, take 2