Truncate and delete adds wal logs for slave to process.

Поиск
Список
Период
Сортировка
От Chris Barnes
Тема Truncate and delete adds wal logs for slave to process.
Дата
Msg-id BLU149-W38E2AD72617D753AFFB755D44E0@phx.gbl
обсуждение исходный текст
Ответы Re: Truncate and delete adds wal logs for slave to process.  (Greg Stark <gsstark@mit.edu>)
Re: Truncate and delete adds wal logs for slave to process.  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-general
 
 
I have a question regaring delete & truncate versus a drop of the tables and recreating it.
 
We have a database that gets recreated each week that is 31 GB in size.
 
The way that it is currently being done is to truncate all of the tables.
 
I would like to confirm.
 
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?
 
 
 
 
 
 


В списке pgsql-general по дате отправления:

Предыдущее
От: Karl Denninger
Дата:
Сообщение: Re: [HACKERS] Bug on pg_lesslog
Следующее
От: John R Pierce
Дата:
Сообщение: Re: problems maintaining boolean columns in a large table