Search Postgresql Archives

Re: Truncate and delete adds wal logs for slave to process.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Feb 11, 2010 at 5:47 PM, Chris Barnes
<compuguruchrisbarnes@xxxxxxxxxxx> 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

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux