Hello,
At Tue, 13 Sep 2016 10:00:32 -0300, Alvaro Herrera
wrote in <20160913130032.GA391646@alvherre.pgsql>
> Michael Paquier wrote:
> > On Tue, Sep 13, 2016 at 10:42 AM, Kyotaro HORIGUCHI
> > wrote:
> > > If we take a policy to try to imitate the behavior of some
> > > reference platform (spec
On Tue, Sep 13, 2016 at 10:00 PM, Alvaro Herrera
wrote:
> Yeah, I looked into this a few days ago and that was my conclusion also:
> let's drop this.
Okay. Just done so in the CF app.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subs
Michael Paquier wrote:
> On Tue, Sep 13, 2016 at 10:42 AM, Kyotaro HORIGUCHI
> wrote:
> > If we take a policy to try to imitate the behavior of some
> > reference platform (specifically Linux) on other platforms, this
> > is required disguising. Another potential policy on this problem
> > is "fol
On Tue, Sep 13, 2016 at 10:42 AM, Kyotaro HORIGUCHI
wrote:
> If we take a policy to try to imitate the behavior of some
> reference platform (specifically Linux) on other platforms, this
> is required disguising. Another potential policy on this problem
> is "following the platform's behavior". Fr
Hello, thanks for revewing and the discussion.
At Sat, 10 Sep 2016 10:44:50 -0400, Tom Lane wrote in
<17326.1473518...@sss.pgh.pa.us>
> Michael Paquier writes:
> > On Fri, Sep 9, 2016 at 11:39 PM, Tom Lane wrote:
> >> So this change would deal nicely with the "peer application on the remote
>
Michael Paquier writes:
> On Fri, Sep 9, 2016 at 11:39 PM, Tom Lane wrote:
>> So this change would deal nicely with the "peer application on the remote
>> host is suddenly stopped" case, at the price of being not nice about any
>> of the other cases. Not convinced it's a good tradeoff.
> Yes, i
On Fri, Sep 9, 2016 at 11:39 PM, Tom Lane wrote:
> Haribabu Kommi writes:
>> On Thu, Jun 2, 2016 at 6:51 PM, Kyotaro HORIGUCHI <
>> horiguchi.kyot...@lab.ntt.co.jp> wrote:
>>> After a process termination without PQfinish() of a client,
>>> server emits the following log message not seen on Linux
Haribabu Kommi writes:
> On Thu, Jun 2, 2016 at 6:51 PM, Kyotaro HORIGUCHI <
> horiguchi.kyot...@lab.ntt.co.jp> wrote:
>> After a process termination without PQfinish() of a client,
>> server emits the following log message not seen on Linux boxes.
>> LOG: could not receive data from client: An e
On Thu, Jun 2, 2016 at 6:51 PM, Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp> wrote:
> Hello.
>
> After a process termination without PQfinish() of a client,
> server emits the following log message not seen on Linux boxes.
>
> > LOG: could not receive data from client: An existing connect
Thank you for the suggestion, I've done it.
At Wed, 15 Jun 2016 12:15:07 -0400, Robert Haas wrote
in
> On Thu, Jun 2, 2016 at 4:51 AM, Kyotaro HORIGUCHI
> wrote:
> > After a process termination without PQfinish() of a client,
> > server emits the following log message not seen on Linux boxes.
On Thu, Jun 2, 2016 at 4:51 AM, Kyotaro HORIGUCHI
wrote:
> After a process termination without PQfinish() of a client,
> server emits the following log message not seen on Linux boxes.
>
>> LOG: could not receive data from client: An existing connection was
>> forcibly closed by the remote host.
Hello.
After a process termination without PQfinish() of a client,
server emits the following log message not seen on Linux boxes.
> LOG: could not receive data from client: An existing connection was forcibly
> closed by the remote host.
This is because pgwin32_recv reuturns an error ECONNRES
12 matches
Mail list logo