On Tue, Mar 16, 2010 at 6:11 PM, Heikki Linnakangas
<heikki.linnakan...@enterprisedb.com> wrote:
> Commmitted. I edited the message and error code a bit:
>
> ereport(FATAL,
> (errcode(ERRCODE_CANNOT_CONNECT_NOW),
> errmsg("recovery is still in progress, can't accept WAL
> streaming connections")));
>
> ERRCODE_CANNOT_CONNECT_NOW is what we use when the system is shutting
> down etc, so that that seems appropriate.
Thanks! I agree that ERRCODE_CANNOT_CONNECT_NOW is more suitable.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
