| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Idle In Transaction Session Timeout, revived |
| Date: | 2016-02-04 10:00:58 |
| Message-ID: | 20160204100058.GA220738@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Steele wrote:
> > <...> But what I think really happens is
> > some badly-written Java application loses track of a connection
> > someplace and just never finds it again. <...>
I've seen that also, plenty of times.
> That's what I've seen over and over again. And then sometimes it's not
> a badly-written Java application, but me, and in that case I definitely
> want the connection killed. Without logging, if you please.
So the way to escape audit logging is to open a transaction, steal some
data, then leave the connection open so that it's not logged when it's
killed?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rushabh Lathia | 2016-02-04 10:44:41 | Re: Optimization for updating foreign tables in Postgres FDW |
| Previous Message | Michael Paquier | 2016-02-04 09:59:03 | Re: In-core regression tests for replication, cascading, archiving, PITR, etc. |