pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Efrain J. Berdecia <ejberdecia@yahoo.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>
Subject: Re: pg_restore enhancements
Date: Wed, 22 Nov 2023 14:27:52 -0500
Message-ID: <2298671.1700681272@sss.pgh.pa.us> (raw)
In-Reply-To: <383739960.7061560.1700672154915@mail.yahoo.com>
References: <362032628.6955904.1700659540303.ref@mail.yahoo.com>
	<362032628.6955904.1700659540303@mail.yahoo.com>
	<cc0c5cf5-4674-46a0-9c20-053aac907faa@aklaver.com>
	<383739960.7061560.1700672154915@mail.yahoo.com>

"Efrain J. Berdecia" <ejberdecia@yahoo.com> writes:
> Thanks, the issue we've run into, which I guess could be really a setup issue, with running a COPY command while executing pg_restore, is that if we are restoring a large table (bigger than 500GB) our WAL directory can grow to be very large.
> I would think that if the pg_restore or COPY command was able to support a batch-size option, this should allow postgres to either archive or remove wal files and prevent having to re-size the WAL directory for a one time refresh operation.
> I'm trying to gage how feasible would be to start looking at contributing to add such a feature to either the COPY command or pg_restore.

Given the shortage of other complaints, I tend to agree with Adrian
that there's not likely to be much interest in adding complexity
to pg_restore (or COPY) to address this.  You should probably look
harder at the idea that you have some configuration problem that's
triggering your WAL bloat.  If COPY can run you out of WAL space,
then so could any future bulk insert or update.

			regards, tom lane





view thread (11+ messages)  latest in thread

Message-ID: <2298671.1700681272@sss.pgh.pa.us>
Permalink:  ../2298671.1700681272@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2298671.1700681272@sss.pgh.pa.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: tgl@sss.pgh.pa.us, ejberdecia@yahoo.com, adrian.klaver@aklaver.com
  Subject: Re: pg_restore enhancements
  In-Reply-To: <2298671.1700681272@sss.pgh.pa.us>
  References: <362032628.6955904.1700659540303.ref@mail.yahoo.com> <362032628.6955904.1700659540303@mail.yahoo.com> <cc0c5cf5-4674-46a0-9c20-053aac907faa@aklaver.com> <383739960.7061560.1700672154915@mail.yahoo.com> <2298671.1700681272@sss.pgh.pa.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