Re: [HACKERS] Windows exit code 128 ... it's baaack

2014-09-17 Thread Andrew Dunstan
On 04/07/2014 10:26 AM, Andres Freund wrote: On 2014-04-05 11:05:09 -0400, Tom Lane wrote: Andres Freund writes: On 2014-02-27 19:14:13 -0500, Tom Lane wrote: I looked at the postmaster log for the ongoing issue on narwhal (to wit, that the contrib/dblink test dies the moment it tries to do

Re: [HACKERS] Windows exit code 128 ... it's baaack

2014-04-07 Thread Andres Freund
On 2014-04-05 11:05:09 -0400, Tom Lane wrote: > Andres Freund writes: > > On 2014-02-27 19:14:13 -0500, Tom Lane wrote: > >> I looked at the postmaster log for the ongoing issue on narwhal > >> (to wit, that the contrib/dblink test dies the moment it tries > >> to do anything dblink-y), and looky

Re: [HACKERS] Windows exit code 128 ... it's baaack

2014-04-05 Thread Tom Lane
Andres Freund writes: > On 2014-02-27 19:14:13 -0500, Tom Lane wrote: >> I looked at the postmaster log for the ongoing issue on narwhal >> (to wit, that the contrib/dblink test dies the moment it tries >> to do anything dblink-y), and looky here what the postmaster >> has logged: > One interesti

Re: [HACKERS] Windows exit code 128 ... it's baaack

2014-04-05 Thread Andres Freund
On 2014-02-27 19:14:13 -0500, Tom Lane wrote: > I looked at the postmaster log for the ongoing issue on narwhal > (to wit, that the contrib/dblink test dies the moment it tries > to do anything dblink-y), and looky here what the postmaster > has logged: One interesting bit about this is that it se

Re: [HACKERS] Windows exit code 128 ... it's baaack

2014-03-01 Thread Amit Kapila
On Fri, Feb 28, 2014 at 5:44 AM, Tom Lane wrote: > I looked at the postmaster log for the ongoing issue on narwhal > (to wit, that the contrib/dblink test dies the moment it tries > to do anything dblink-y), and looky here what the postmaster > has logged: > > 530fc965.bac:2] LOG: server process