pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joe Conway <mail@joeconway.com>
To: Josef Machytka <josef.machytka@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash with "ERROR: unknown error"
Date: Fri, 23 Dec 2016 07:54:22 -0800
Message-ID: <fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com> (raw)
In-Reply-To: <CAGvVEFt8Gb2ANBb2RnLMJMagyBMDpP7ebYjHoZ5WRG0eB6D5qg@mail.gmail.com>
References: <20161221094443.25614.47807@wrigleys.postgresql.org>
	<6818.1482333970@sss.pgh.pa.us>
	<CAGvVEFs1QxgFLUmc2aasrLYQS5MQhW_v4oV13i15Mph9Cwiugg@mail.gmail.com>
	<18191.1482336664@sss.pgh.pa.us>
	<CAGvVEFt8Gb2ANBb2RnLMJMagyBMDpP7ebYjHoZ5WRG0eB6D5qg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-bugs>

On 12/23/2016 01:08 AM, Josef Machytka wrote:
> Hi again.
> So I checked all logs and it turned out one of databases involved vent
> into recovery mode because some of its connections was killed.
> Probably out of memory killer did it. So it caused chain reaction. And
> billing query was canceled "due to administration command" and it was
> shown through dblink as "unknown error".
> Which looked quite horrible...

FYI, I committed a fix for this since the initial report.

Before:
----------
test=# -- kill the remote side manually
test=# select * from dblink('dbname=test','select pg_sleep(30)');
ERROR:  unknown error
CONTEXT:  Error occurred on dblink connection named "unnamed": could not
execute query.


After:
----------
test=# -- kill the remote side manually
test=# select * from dblink('dbname=test','select pg_sleep(30)');
ERROR:  server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

CONTEXT:  Error occurred on dblink connection named "unnamed": could not
execute query.

Joe

-- 
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

Attachments:

  signature.asc (application/pgp-signature, 818B) download

view thread (8+ messages)

Message-ID: <fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com>
Permalink:  ../fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com/
Also on:    postgresql.org/message-id/fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: mail@joeconway.com, josef.machytka@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash with "ERROR: unknown error"
  In-Reply-To: <fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox