From: Jona <jonanews@oismail.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Dennis Bjorklund <db@zigo.dhs.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Query plan changes after pg_dump / pg_restore
Date: Thu, 09 Jun 2005 11:23:14 +0200
Message-ID: <42A80A82.3060900@oismail.com> (raw)
In-Reply-To: <42A803E2.8000706@familyhealth.com.au>
References: <Pine.LNX.4.44.0506090918100.25939-100000@zigo.dhs.org>
<42A7F9D9.8000004@oismail.com>
<42A7FD12.2080608@familyhealth.com.au>
<42A803C8.6070507@oismail.com>
<42A803E2.8000706@familyhealth.com.au>
It's the same (physical) server as well as the same PostGreSQL daemon,
so yes.
The only difference is the actual database, the test database is made
from a backup of the live database and restored onto the same PostGreSQL
server.
So if I run "show databases" in psql i get:
- test
- live
Makes sense??
/Jona
Christopher Kings-Lynne wrote:
> Is effective_cache_size set the same on the test and live?
>
> Jona wrote:
>
>> Thanks... have notified our sys admin of that so he can make the
>> correct changes.
>>
>> It still doesn't explain the difference in query plans though?
>>
>> I mean, it's the same database server the two instances of the same
>> database is running on.
>> One instance (the live) just insists on doing the seq scan of the 50k
>> records in Price_Tbl and the 6.5k records in SCT2SubCatType_Tbl.
>> Seems weird....
>>
>> Cheers
>> Jona
>>
>> Christopher Kings-Lynne wrote:
>>
>>>> Thank you for the swift reply, the following is the output of the
>>>> SHOW ALL for shared_buffers and effective_cache_size.
>>>> shared_buffers: 13384
>>>> effective_cache_size: 4000
>>>> server memory: 2GB
>>>
>>>
>>>
>>>
>>> effective_cache_size should be 10-100x larger perhaps...
>>>
>>> Chris
>>
>>
>>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
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: jonanews@oismail.com, chriskl@familyhealth.com.au, db@zigo.dhs.org
Subject: Re: Query plan changes after pg_dump / pg_restore
In-Reply-To: <42A80A82.3060900@oismail.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