pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Ron <ronljohnsonjr@gmail.com>
Cc: pgsql-general@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Subject: Re: Pg 16: will pg_dump & pg_restore be faster?
Date: Tue, 30 May 2023 22:11:38 -0400
Message-ID: <ZHas2gDlXBqZG/US@momjian.us> (raw)
In-Reply-To: <CAApHDvrQ1bpzyS8k=nHsL0rNFNOkiGmiJRQGO4jUb4yPS4EysQ@mail.gmail.com>
References: <7e1a8736-d74c-8de1-679f-f47b250a13cc@gmail.com>
	<CAApHDvoD-QsDzqKEMpG07dWU=5g1ZWSK_tjR5mC=a+79ZudddA@mail.gmail.com>
	<ZHafJF3FadgFr/5A@momjian.us>
	<CAApHDvrQ1bpzyS8k=nHsL0rNFNOkiGmiJRQGO4jUb4yPS4EysQ@mail.gmail.com>

On Wed, May 31, 2023 at 02:05:10PM +1200, David Rowley wrote:
> On Wed, 31 May 2023 at 13:13, Bruce Momjian <bruce@momjian.us> wrote:
> > There is no mention of concurrency being a requirement.  Is it wrong?  I
> > think there was a question of whether you had to add _multiple_ blocks
> > ot get a benefit, not if concurrency was needed.  This email about the
> > release notes didn't mention the concurrent requirement:
> 
> My understanding had been that concurrency was required, but I see the
> commit message for 00d1e02be mentions:
> 
> > Even single threaded
> > COPY is measurably faster, primarily due to not dirtying pages while
> > extending, if supported by the operating system (see commit 4d330a61bb1).
> 
> If that's the case then maybe the beta release notes could be edited
> slightly to reflect this. Maybe something like:
> 
> "Relation extensions have been improved allowing faster bulk loading
> of data using COPY. These improvements are more significant when
> multiple processes are concurrently loading data into the same table."

The release notes don't normally get into details on the magnitude of
the improvement in various circumstances.

> The current text of "PostgreSQL 16 can also improve the performance of
> concurrent bulk loading of data using COPY up to 300%." does lead me
> to believe that nothing has been done to improve things when only a
> single backend is involved.

Yes, agreed.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.





view thread (11+ messages)  latest in thread

Message-ID: <ZHas2gDlXBqZG/US@momjian.us>
Permalink:  ../ZHas2gDlXBqZG%2FUS@momjian.us/
Also on:    postgresql.org/message-id/ZHas2gDlXBqZG/US@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: bruce@momjian.us, dgrowleyml@gmail.com, jkatz@postgresql.org, ronljohnsonjr@gmail.com, andres@anarazel.de
  Subject: Re: Pg 16: will pg_dump & pg_restore be faster?
  In-Reply-To: <ZHas2gDlXBqZG/US@momjian.us>
  References: <7e1a8736-d74c-8de1-679f-f47b250a13cc@gmail.com> <CAApHDvoD-QsDzqKEMpG07dWU=5g1ZWSK_tjR5mC=a+79ZudddA@mail.gmail.com> <ZHafJF3FadgFr/5A@momjian.us> <CAApHDvrQ1bpzyS8k=nHsL0rNFNOkiGmiJRQGO4jUb4yPS4EysQ@mail.gmail.com> <ZHas2gDlXBqZG/US@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox