From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_receivewal and messages printed in non-verbose mode |
Date: | 2017-06-13 06:33:32 |
Message-ID: | CAB7nPqSG0yirmwRcEXqHXCpqjuyK+NYmn_z8ACFN24Ob4jthow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi all,
I have noticed that the following messages can show up from
pg_receivewal even if the verbose mode is not used:
if (prevtimeline != 0 && prevtimeline != timeline)
fprintf(stderr, _("%s: switched to timeline %u at %X/%X\n"),
progname, timeline,
(uint32) (prevpos >> 32), (uint32) prevpos);
if (time_to_abort)
{
fprintf(stderr, _("%s: received interrupt signal, exiting\n"),
progname);
return true;
}
Those come from stop_streaming in pg_receivewal.c. Shouldn't those
messages only show up to the user if --verbose is used? It seems
strange to me that at least the first one is written to the user as
that's not an error after promoting a standby.
Thanks,
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-06-13 06:33:40 | Re: Get stuck when dropping a subscription during synchronizing table |
Previous Message | Masahiko Sawada | 2017-06-13 06:08:10 | Re: pg_subscription_rel entry can be updated concurrently |