| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Subject: | Re: Streaming replication and unfit messages |
| Date: | 2010-02-18 08:23:17 |
| Message-ID: | 201002180923.20434.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday 18 February 2010 06:17:06 Fujii Masao wrote:
> > [2460]: LOG: could not receive data from client: No connection could be
> > made because the target machine actively refused it. [2460]: FATAL:
> > invalid standby closing message type 4
> > [2460]: LOG: could not send data to client: No connection could be made
> > because the target machine actively refused it.
>
> Also the walsender wrongly tries to send the FATAL message to the standby
> even though the connection has already been closed, and then gets the
> following LOG message after the FATAL one. This FATAL message is suitable,
> but output of the LOG message looks messy, too. We should use COMMERROR
> instead of FATAL and then just call proc_exit() in order to prevent a
> message from being sent?
Or hope for my idle query cancellation prelim. patch to get applied so you can
do ereport(FATAL | LOG_NO_CLIENT, ...) ;-)
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2010-02-18 08:26:51 | Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl |
| Previous Message | Heikki Linnakangas | 2010-02-18 07:38:15 | Re: Streaming replication on win32, still broken |