From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | Chris Barnes <compuguruchrisbarnes(at)hotmail(dot)com> |
Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Truncate and delete adds wal logs for slave to process. |
Date: | 2010-02-11 22:15:16 |
Message-ID: | 407d949e1002111415q349dca63vb10c9af3428fa650@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Feb 11, 2010 at 5:47 PM, Chris Barnes
<compuguruchrisbarnes(at)hotmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Koichi Suzuki | 2010-02-11 22:39:23 | Re: [GENERAL] [HACKERS] Bug on pg_lesslog |
Previous Message | Vick Khera | 2010-02-11 22:01:37 | Re: Deadlock Detected |