Log level of logical decoding

From: Francesco Nidito <frnidito(at)live(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Log level of logical decoding
Date: 2018-11-30 15:10:50
Message-ID: VI1PR0902MB212742DCEE572F06A2BA2EA6A6D30@VI1PR0902MB2127.eurprd09.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hi All,

With reference to an old thread (https://www.postgresql.org/message-id/8307.1419439826%40sss.pgh.pa.us), our application polls the database instance periodically to check if there are new transaction in the WAL waiting to be processed. As a consequence of this, our log file is full of messages like

2018-11-30 10:37:29 UTC LOG: starting logical decoding for slot "test_slot"
2018-11-30 10:37:29 UTC DETAIL: streaming transactions committing after 4AC/41D5F950, reading WAL from 4AC/41C16868
2018-11-30 10:37:29 UTC STATEMENT:
SELECT * FROM pg_logical_slot_peek_changes('test_slot', NULL, NULL,
'include-timestamp', '1', 'skip-empty-xacts', '1')

As those logs are of dubious utility, and following the comment of Tom in the last email of the old thread, I would like to ask why this message is a LOG and not a DEBUG and if there is any plan to make them DEBUG?

Thanks a lot in advance!

Francesco

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2018-11-30 15:33:27 Re: surprising query optimisation
Previous Message Slavcho Trnkovski 2018-11-30 13:11:10 postgis after pg_upgrade

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2018-11-30 15:13:13 Re: Undo worker and transaction rollback
Previous Message Dmitry Dolgov 2018-11-30 15:05:35 Re: [HACKERS] Lazy hash table for XidInMVCCSnapshot (helps Zipfian a bit)