| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| 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 14:43:21 |
| Message-ID: | 56B36389.4000807@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/4/16 5:00 AM, Alvaro Herrera wrote:
> 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?
Well, of course I was joking, but even so I only meant the disconnect
shouldn't be logged to save me embarrassment.
But you are probably joking as well. Oh, what a tangled web.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2016-02-04 14:51:25 | Re: Support for N synchronous standby servers - take 2 |
| Previous Message | Fujii Masao | 2016-02-04 14:34:24 | Re: Support for N synchronous standby servers - take 2 |