From: Greg Smith <gsmith@gregsmith.com>
To: kelvan <kicmcewen@windowslive.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: database tuning
Date: Tue, 11 Dec 2007 19:07:38 -0500 (EST)
Message-ID: <Pine.GSO.4.64.0712111855520.21402@westnet.com> (raw)
In-Reply-To: <fjn2d5$5al$1@news.hub.org>
References: <fja1je$2c22$1@news.hub.org>
<1197016760.4255.474.camel@ebony.site>
<fjc2hb$2cd3$1@news.hub.org>
<dcc563d10712100858j7b55e68co5d0da0f8b82c19b1@mail.gmail.com>
<fjki5a$uf1$1@news.hub.org>
<Pine.GSO.4.64.0712101912340.14776@westnet.com>
<fjn2d5$5al$1@news.hub.org>
On Wed, 12 Dec 2007, kelvan wrote:
> my original question is what are the overheads for postgres but obviously no
> one knows or no one knows where a webpage containing this information is -_-
In addition to the documentation links people have already suggested, I'd
also suggest
http://andreas.scherbaum.la/blog/archives/282-table-size,-database-size.html
which gives some helpful suggestions on measuring the actual size of data
you've got in the database already. It's possible to make a mistake when
trying to compute overhead yourself; loading a subset of the data and
measuring the size is much less prone to error.
> if we were not using a Mac we would have none of the problems we have
> with connection issues such as php seems to want to take up 20 db
> connections at a time
I can't imagine why the connection pooling links I suggested before
wouldn't work perfectly fine on a Mac. You're correct to first nail down
why PHP is connecting more than you expect, but eventually I suspect
you'll need to wander toward pooling.
> neither I nor the web app developer are Mac savvy hell as far as we have
> seen no Mac tec is Mac savvy either
:)
> we cannot get parts of postgres to run on a Mac either such as pgagent
> which is necessary for us but we cannot seem to find a daemon that works
> on a Mac
You might want to give some specifics and ask about this on the pgAdmin
mailing list: http://www.pgadmin.org/support/list.php
OS X support is relatively recent for pgAdmin and I see some other recent
fixes for specific issues on that platform.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gsmith@gregsmith.com, kicmcewen@windowslive.com
Subject: Re: database tuning
In-Reply-To: <Pine.GSO.4.64.0712111855520.21402@westnet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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