On Mon, 2004-07-12 at 10:26, Konstantin Pelepelin wrote:
> The
> > > best solution I see is having an (per session)
> > > idle_transaction_timeout or idle_connection_timeout
> > > setting. But there is no such thing in postgres!
> > > Scanning through list I've not found any workaround.
Have you looked at statement_timeout?
This doesn't do exactly what you want, but is close enough.
If you don't have it at your release, upgrade.
> > Looking into TODO I don't see any plans for it.
> > > Is it too difficult implementing or I've missed
> > > something or are there workarounds?
This might be something you could do...
Best regards, Simon Riggs
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
