Re: pg_restore enhancements

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: "Efrain J(dot) Berdecia" <ejberdecia(at)yahoo(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Subject: Re: pg_restore enhancements
Date: 2023-11-23 08:37:11
Message-ID: 368f73d6c7a1530d82f9c1c12a2cd0a14780b37a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2023-11-22 at 16:55 +0000, Efrain J. Berdecia wrote:
> 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.

You can avoidwriting WAL if you set "wal_level = minimal", restart PostgreSQL
and restore the dump with the --single-transaction option.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2023-11-23 08:40:28 Re: strange behavior of pg_hba.conf file
Previous Message Cherry Pang 2023-11-23 06:56:39 Inquiry Regarding Initial Seed for pgsql Protocol Fuzz Testing