Re: pg_restore enhancements - Mailing list pgsql-general

From Laurenz Albe
Subject Re: pg_restore enhancements
Date
Msg-id 368f73d6c7a1530d82f9c1c12a2cd0a14780b37a.camel@cybertec.at
Whole thread Raw
In response to Re: pg_restore enhancements  ("Efrain J. Berdecia" <ejberdecia@yahoo.com>)
Responses Re: pg_restore enhancements  (Ron Johnson <ronljohnsonjr@gmail.com>)
List 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



pgsql-general by date:

Previous
From: Cherry Pang
Date:
Subject: Inquiry Regarding Initial Seed for pgsql Protocol Fuzz Testing
Next
From: Laurenz Albe
Date:
Subject: Re: strange behavior of pg_hba.conf file