Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.postgresql > #442
| From | gargoyle60 <gargoyle60@example.invalid> |
|---|---|
| Newsgroups | comp.databases.postgresql |
| Subject | Re: Preventing a timeout on a connection |
| Date | 2013-03-01 13:16 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <7fa1j8lmnlcug5mt87hf0inohsb7cilva0@4ax.com> (permalink) |
| References | <6f9ui8pi4ub903fl62kgg4t6793c5ph7b7@4ax.com> |
Thanks for the responses. Using the libpq functions with connection parameters seems one possible idea. However, I am trying to keep my application as generic as possible and avoid vendor-specific behaviour inside the application (it currently uses a façade to handle multi-vendor databases, with postgres as my preferred choice). I suppose I could develop a stored procedure and invoke/call libpq within that, as appropriate? Presently my application has its own #keepAlive method (simple issues a 'SELECT 1 AS "selected";') that I can enhance via a fork process to remain active on my connection. I shall consider both solutions. I was hoping for a conf-file parameter, but c'est la vie!
Back to comp.databases.postgresql | Previous | Next — Previous in thread | Find similar | Unroll thread
Preventing a timeout on a connection gargoyle60 <gargoyle60@example.invalid> - 2013-02-28 09:41 +0000 Re: Preventing a timeout on a connection "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2013-02-28 11:03 +0100 Re: Preventing a timeout on a connection Jasen Betts <jasen@xnet.co.nz> - 2013-02-28 11:00 +0000 Re: Preventing a timeout on a connection gargoyle60 <gargoyle60@example.invalid> - 2013-03-01 13:16 +0000
csiph-web