Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: How to monitor resources on Linux.
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Jeff Frost" <jeff(at)frostconsultingllc(dot)com>
- Cc: "'John R Allgood'" <jallgood(at)the-allgoods(dot)net>, "'Andrew Sullivan'" <ajs(at)crankycanuck(dot)ca>, pgsql-admin(at)postgresql(dot)org
- Subject: Re: How to monitor resources on Linux.
- Date: Wed, 29 Aug 2007 13:57:37 -0400
"Jeff Frost" <jeff(at)frostconsultingllc(dot)com> writes: > Maybe you could use pgpool or something similar to allow it to think it's > connecting locally and still move it off the actual postgresql server? Actually, I don't see anything very wrong with running a 32-bit database executable, so long as you don't have ambitions to have more than a GB or so of shared_buffers. The thing that's not good is a 32-bit kernel. regards, tom lane
- References:
- Re: How to monitor resources on Linux.
- From: jallgood
- Re: How to monitor resources on Linux.
- From: Tom Lane
- Re: How to monitor resources on Linux.
- From: John R Allgood
- Re: How to monitor resources on Linux.
- From: Andrew Sullivan
- Re: How to monitor resources on Linux.
- From: John R Allgood
- Re: How to monitor resources on Linux.
- From: Jeff Frost
- Re: How to monitor resources on Linux.
- Prev by Date: Re: vacuum killed because of out of memory
- Next by Date: could not create IPv6 socket when starting Postgres server
- Previous by thread: Re: How to monitor resources on Linux.
- Next by thread: Re: How to monitor resources on Linux.
- Indexes: