diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-03-14 12:47:46 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-03-14 12:47:53 -0400 |
| commit | 5ed6fff6b729c3cce55d4abc8f695da93aa40a0d (patch) | |
| tree | 92221a98d22c6e408c8c2f988da6dd8d37e76305 /contrib/postgres_fdw/sql/postgres_fdw.sql | |
| parent | c6c099d31abd5ae22265787d4ab5fc9b3f563c87 (diff) | |
| download | postgresql-5ed6fff6b729c3cce55d4abc8f695da93aa40a0d.tar.gz postgresql-5ed6fff6b729c3cce55d4abc8f695da93aa40a0d.zip | |
Make logging about multixact wraparound protection less chatty.
The original messaging design, introduced in commit 068cfadf9, seems too
chatty now that some time has elapsed since the bug fix; most installations
will be in good shape and don't really need a reminder about this on every
postmaster start.
Hence, arrange to suppress the "wraparound protections are now enabled"
message during startup (specifically, during the TrimMultiXact() call).
The message will still appear if protection becomes effective at some
later point.
Discussion: https://postgr.es/m/17211.1489189214@sss.pgh.pa.us
Diffstat (limited to 'contrib/postgres_fdw/sql/postgres_fdw.sql')
0 files changed, 0 insertions, 0 deletions