Re: Killing inactive connections

Hi,

From what I gather, your "feature" should be placed in the client and
not on the server... Therefore, if you had an MS Access or some other
application, accessing your backend server, and your APPLICATION is
being idle for N time units, then you can set your APPLICATION to log
the user out. At least, that's how I would approach it..;-)

Hope that helps...;-)

Cheers,

John Clark

Andrew Gould wrote:
>
> I run a clinical data warehouse using PostgreSQL
> 7.1.2_2 on FreeBSD 4.3-stable. Data security and
> privacy standards have been enacted at the federal
> level via the Health Insurance Portability and
> Accountability Act (HIPAA).
>
> One of the rules requires timed logouts. If someone
> walks away from their desk for a certain amount of
> time, the connection should time-out; and the employee
> must log back into the application.
>
> Data analysts access my databases using MS Access. Is
> there a way in PostgreSQL to track inactivity and
> close inactive connections after a specified length of
> time?
>

--
/) John Clark Naldoza y Lopez (\
/ ) Software Design Engineer III ( \
_( (_ _ Web-Application Development _) )_
(((\ \> /_> Cable Modem Network Management System <_\ </ /)))
(\\\\ \_/ / NEC Telecom Software Phils., Inc. \ \_/ ////)
\ / \ /
\ _/ phone: (+63 32) 233-9142 loc. 3113 \_ /
/ / cellphone: (+63 919) 399-4742 \ \
/ / email: njclark(at)ntsp(dot)nec(dot)co(dot)jp \ \

"Intelligence is the ability to avoid doing work, yet getting the work
done"
--Linus Torvalds