Re: Advice on logging strategy

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема Re: Advice on logging strategy
Дата
Msg-id CAMkU=1w9BU4Z7tsoB0xrQuAROB61TD0FunCVNqt58OnD1gw=5A@mail.gmail.com
обсуждение исходный текст
Ответ на Advice on logging strategy  (Mike Martin <redtux1@gmail.com>)
Список pgsql-general
Дерево обсуждения
On Thu, Oct 11, 2018 at 6:27 AM Mike Martin <redtux1@gmail.com> wrote:
I have a question on logging strategy

I have loggin set to
log_statement = 'all' on a network database with logging set to csv so I can import it to a logging table

However the database is populated via a nightly routine downloading data via REST APIusing prepared statements

This results in enormous log files which take ages to import using copy becuase each execute statement is logged with the parameters chosen

Is there any way around this?

One option is to convert to using COPY...FROM STDIN rather than prepared INSERTs.

Another is to create a user specifically for bulk population, and do a 'ALTER USER bulk_load SET log_statement=none` to override the global log_statement setting.

Cheers,

Jeff

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

Предыдущее
От: Alban Hertroys
Дата:
Сообщение: Re: Want to acquire lock on tables where primary of one table isforeign key on othere
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: RHEL 7 (systemd) reboot