pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
How to Control the Persistence of A PostgreSQL Connection
2+ messages / 2 participants
[nested] [flat]

* How to Control the Persistence of A PostgreSQL Connection
@ 2005-08-18 17:46  Lane Van Ingen <lvaningen@esncc.com>
  0 siblings, 1 reply; 2+ messages in thread

From: Lane Van Ingen @ 2005-08-18 17:46 UTC (permalink / raw)
  To: pgsql-admin

Have been reading the manual and searching for connection timeout
information, but
I don't think what I have found answers my questions. Most of what I found
so far
is C library functions in Chapter 27 on version 8.0 manual (am not a C
programmer).

I saw connection timeout discussed a little bit with login / authentication
type
parameters, but it had to do with getting in, not maintaining a connection.

We are connecting to PostgreSQL using clients running JBOSS. What I want to
know is:
  - from the PostgreSQL side, how long will a connection to the database be
kept open
    if inactive for a period of time, and where are the parameter(s) to
affect that?
  - does PostgreSQL do connection pooling?
  - is there any way I can tell if I am getting into trouble on the number
of
    connections open, and how long they have been open, outside of user
complaints
    of lack of service (unable to connect)?

I am on Windows 2003, using version 8.0.





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: How to Control the Persistence of A PostgreSQL Connection
@ 2005-08-18 18:10  Guido Barosio <gbarosio@gmail.com>
  parent: Lane Van Ingen <lvaningen@esncc.com>
  0 siblings, 0 replies; 2+ messages in thread

From: Guido Barosio @ 2005-08-18 18:10 UTC (permalink / raw)
  To: Lane Van Ingen <lvaningen@esncc.com>; +Cc: pgsql-admin

While this is strictly related to the administration of a rdbms, I don't 
actully know if it is a matter of the rdbms software to control the 
connection timeout. (This is something that major rdbms providers, oracle, 
ms, give as a solution, but I am not sure if that is a good habit, asuming 
that in production enviroment you will have a firewall and may be also 
network configurations that may affect the rdbms connection behaviour. But I 
guess this is a new discussion, and won't help with your current problem ;) 
)
 As far as I know, this would go hand on hand with "under the bridge" tcp/ip 
settings. (A few days ago a discussion run against a similar issue, look for 
it in the archives)
 Now, postgresql does not has a native pooling method (or no that I am aware 
of), but you will find many third party solutions for that.
 In the postgresql.conf file, you will find a parameter max_connections or 
alike, where you will have to play with that value, as well as with your 
memory resources parameters. Remember that connections and memory usage are 
close in hands, to make the thing work.
 My poor contribution :)
 Best wishes,
Guido

 On 8/18/05, Lane Van Ingen <lvaningen@esncc.com> wrote: 
> 
> Have been reading the manual and searching for connection timeout
> information, but
> I don't think what I have found answers my questions. Most of what I found
> so far
> is C library functions in Chapter 27 on version 8.0 manual (am not a C
> programmer).
> 
> I saw connection timeout discussed a little bit with login / 
> authentication
> type
> parameters, but it had to do with getting in, not maintaining a 
> connection.
> 
> We are connecting to PostgreSQL using clients running JBOSS. What I want 
> to
> know is:
> - from the PostgreSQL side, how long will a connection to the database be
> kept open
> if inactive for a period of time, and where are the parameter(s) to
> affect that?
> - does PostgreSQL do connection pooling?
> - is there any way I can tell if I am getting into trouble on the number
> of
> connections open, and how long they have been open, outside of user
> complaints
> of lack of service (unable to connect)?
> 
> I am on Windows 2003, using version 8.0.
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
> 



-- 
"Adopting the position that you are smarter than an automatic
optimization algorithm is generally a good way to achieve less
performance, not more" - Tom Lane.

^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2005-08-18 18:10 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-08-18 17:46 How to Control the Persistence of A PostgreSQL Connection Lane Van Ingen <lvaningen@esncc.com>
2005-08-18 18:10 ` Guido Barosio <gbarosio@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox