From: Kynn Jones <kynnjo@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Joins and DELETE FROM
Date: Tue, 11 Mar 2008 11:56:55 -0400
Message-ID: <c2350ba40803110856t3f0593a1r3c0a317bce2e080a@mail.gmail.com> (raw)
In-Reply-To: <6359.1205006926@sss.pgh.pa.us>
References: <c2350ba40803080931y363d6fd9oaaca11a0ea4f1b79@mail.gmail.com>
<47D2D485.9040103@enterprisedb.com>
<c2350ba40803081102v14d7c3f0u349fb361351fec5a@mail.gmail.com>
<6359.1205006926@sss.pgh.pa.us>
Thank you for your post. I finally spent some quality time with the query
planner section in the docs' server config chapter. Very instructive, even
considering that most of it went over my head!
On Sat, Mar 8, 2008 at 4:08 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
...have you got effective_cache_size set to something that's realistic for
> your machine?
I guess not. It was the default value (128MB) on a machine with 4GB of RAM.
It's not a dedicated server, though, so I'll set it to 1G for now.
But before doing so I need a clarification. The docs state that this
parameter is used only for cost estimation, and has no effect on actual
memory allocations. I imagine that if other memory-related settings are not
somehow in line with it, it could lead to estimates that are out of touch
with reality. If this is correct what other memory-related parameters do I
need to adjust to ensure that both the planner's estimates and the actual
execution agree and fit well with the available memory?
One problem with this test is that your smaller tables probably fit in
> memory whereas the big ones may not, so it's not a given that your test
> accurately reflects how the real query will go down.
>
That's a very helpful reminder. Thanks.
Kynn
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: kynnjo@gmail.com, tgl@sss.pgh.pa.us, heikki@enterprisedb.com
Subject: Re: Joins and DELETE FROM
In-Reply-To: <c2350ba40803110856t3f0593a1r3c0a317bce2e080a@mail.gmail.com>
References: <c2350ba40803080931y363d6fd9oaaca11a0ea4f1b79@mail.gmail.com> <47D2D485.9040103@enterprisedb.com> <c2350ba40803081102v14d7c3f0u349fb361351fec5a@mail.gmail.com> <6359.1205006926@sss.pgh.pa.us> <c2350ba40803110856t3f0593a1r3c0a317bce2e080a@mail.gmail.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