Search Postgresql Archives

Re: Performance opportunities for write-only audit tables?

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

 



On Thursday, May 24, 2018, Andrew Bartley <ambartley@xxxxxxxxx> 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.

[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