Re: BUG #15598: PostgreSQL Error Code is not reported when connection terminated due to idle-in-transaction timeout

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mba(dot)ogolny(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15598: PostgreSQL Error Code is not reported when connection terminated due to idle-in-transaction timeout
Date: 2019-01-18 16:45:02
Message-ID: 25293.1547829902@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
> postgres=# SET idle_in_transaction_session_timeout=500;
> SET
> postgres=# BEGIN;
> BEGIN
> postgres=# SELECT * FROM pg_class;
> FATAL: 25P03: terminating connection due to idle-in-transaction timeout
> LOCATION: ProcessInterrupts, postgres.c:2996
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.

This is not the default appearance of psql error reports.
I'd venture that you are setting VERBOSITY=verbose in your
environment, perhaps in ~/.psqlrc. If you want the same
behavior on your Windows machine, you need to do that there too.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2019-01-18 18:08:33 Re: BUG #15587: Partitions with ALTER TABLE ADD CONSTRAINT
Previous Message PG Bug reporting form 2019-01-18 15:31:25 BUG #15598: PostgreSQL Error Code is not reported when connection terminated due to idle-in-transaction timeout