Subject: Re: BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash
 with "ERROR: unknown error"
To: Josef Machytka <josef.machytka@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
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>
Cc: pgsql-bugs@postgresql.org
From: Joe Conway <mail@joeconway.com>
Openpgp: id=4EA5B4659ED59CC9538139A5332B7E68B699434A
Message-ID: <fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com>
Date: Fri, 23 Dec 2016 07:54:22 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: 
 <CAGvVEFt8Gb2ANBb2RnLMJMagyBMDpP7ebYjHoZ5WRG0eB6D5qg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="rwp8GUtlFujUfBeMf6MbNvrPlWOMMJwlX"
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--rwp8GUtlFujUfBeMf6MbNvrPlWOMMJwlX
From: Joe Conway <mail@joeconway.com>
To: Josef Machytka <josef.machytka@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@postgresql.org
Message-ID: <fea1aaa0-a26c-c1ac-390e-9be7620b6011@joeconway.com>
Subject: Re: [BUGS] BUG #14471: PostgreSQL 9.6 "NOT IN" in select causes crash
 with "ERROR: unknown error"
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>
In-Reply-To: <CAGvVEFt8Gb2ANBb2RnLMJMagyBMDpP7ebYjHoZ5WRG0eB6D5qg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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=3D# -- kill the remote side manually
test=3D# select * from dblink('dbname=3Dtest','select pg_sleep(30)');
ERROR:  unknown error
CONTEXT:  Error occurred on dblink connection named "unnamed": could not
execute query.


After:
----------
test=3D# -- kill the remote side manually
test=3D# select * from dblink('dbname=3Dtest','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

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


--rwp8GUtlFujUfBeMf6MbNvrPlWOMMJwlX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYXUivAAoJEDfy90M199hlSKQQAIXeLWjoGIdHM6CJUZlfdqlj
5WEcP3JxuVZ9zlP5Dkbiw9yH2bGiZU8xc9Run5b6gw8UDh3oAPM8kyQgyF5qtjA3
twCpnv0wVXkNNgR5gygx5CYwPqIyI7btMJlOaRPvy5pBxsAQO2JOBaTV2MGs60C+
Gp+ru7TvN4iveaNsxYvlRaHaF42t5tWs1vK+WDUfbhHviTRnYHfBf7XfS24+0C6W
vCl8iqPqFb+sfsD6Xz1cXHbRt7oppy6vn4tbz7zDQhMb4/hOcq8TVTZ52JyZfOcP
SKBEBjAdOvVb5iDKwzjLfwQu1KNaMYl2+CdDQBh+P4jo2PWVZmIsMo/FN1fPfaep
wD6n4oaF+CQ5Kl+En9RHtiZfS3fhaXYZwtYLu5K1NCe8Ef99HjsVaG8qcrs6nKBp
aGGphTZ637r/xTP3BkoZsWXY/M6kEF7d955b7I90sXFEc+5dO3k0p9/9N+vcfXsY
iK7eCOp4KdqDOipEXweaQm4xThV4ZVcgs2NK35aF8VyGwEAAArhUsVpUEESND7Vo
pHQ6WKJmpzpoBQ6UbDuXU6Txw9N+/VrXuOZlk5SLKEXfrbOfS0evwt6U6p0mgmpA
Om4BR9egb4XuFvRGWo8X8Lv97/97GHs6jOjAB2/ZoNfUJpzkGbGN0E8VvpvsPUtM
Mo1fzqb2IsCu6aXBP6TG
=IRsN
-----END PGP SIGNATURE-----

--rwp8GUtlFujUfBeMf6MbNvrPlWOMMJwlX--