Log level of logical decoding

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Log level of logical decoding

Francesco Nidito
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