Re: Truncate and delete adds wal logs for slave to process. - Mailing list pgsql-general

From Greg Stark
Subject Re: Truncate and delete adds wal logs for slave to process.
Date
Msg-id 407d949e1002111415q349dca63vb10c9af3428fa650@mail.gmail.com
Whole thread Raw
In response to Truncate and delete adds wal logs for slave to process.  (Chris Barnes <compuguruchrisbarnes@hotmail.com>)
List pgsql-general
On Thu, Feb 11, 2010 at 5:47 PM, Chris Barnes
<compuguruchrisbarnes@hotmail.com> wrote:
>
> Because both truncate and delete, I would think that this action would be
> put into the pg_log as a log file that can be rolled back. And, when
> complete, it would be shipped to the standby to be processed?
>
> To reduce this logging, shipping and processing would it be smarter to have
> the tables dropped and recreated?

Truncate will generate about the same amount of log data as dropping
and creating the table.

Delete will generate quite a bit more, but still much less than 31G.
It will also leave you needing to vacuum and reindex more often.

--
greg

pgsql-general by date:

Previous
From: Vick Khera
Date:
Subject: Re: Deadlock Detected
Next
From: Koichi Suzuki
Date:
Subject: Re: [HACKERS] Bug on pg_lesslog