Skip site navigation (1) Skip section navigation (2)

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: 2007-08-29 17:57:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"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

In response to

pgsql-admin by date

Next:From: Jessica RichardDate: 2007-08-29 19:10:05
Subject: could not create IPv6 socket when starting Postgres server
Previous:From: Scott MarloweDate: 2007-08-29 17:43:50
Subject: Re: vacuum killed because of out of memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group