Re: Performance opportunities for write-only audit tables?

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Performance opportunities for write-only audit tables?
Дата
Msg-id CAKFQuwaCw9ZVXw_YerWVbReEKcQW4uj2q3O5WuQj=ntpAp2Frw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Performance opportunities for write-only audit tables?  (Andrew Bartley <ambartley@gmail.com>)
Ответы Re: Performance opportunities for write-only audit tables?  (Andrew Bartley <ambartley@gmail.com>)
Список pgsql-general
On Thursday, May 24, 2018, Andrew Bartley <ambartley@gmail.com> wrote:
Hi,

The two main techniques we use are.

The idea here is to backup the rest of your DB to one backup regime and the log tables to another. We set it up so at the end of the day the current log table is backed up and loaded into an backup archive, then we vacuum freeze the log table.

Yeah, doing logging in-database for immediate performance while periodically copying or moving said data to external storage seems like the best option.  Depends on the definition of an acceptable process and response time should the audit data be needed though.
 

2. Use  UNLOGGED in the log table creates.

Seriously?  For audit tables?

David J.

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
Следующее
От: Andrew Bartley
Дата:
Сообщение: Re: Performance opportunities for write-only audit tables?