From: | Mattthew Lunnon <mlunnon(at)rwa-net(dot)co(dot)uk> |
---|---|
To: | "<pgsql-performance(at)postgresql(dot)org>" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Performance difference between Slon master and slave |
Date: | 2015-12-14 21:43:44 |
Message-ID: | 0393B1AA-B274-4293-825B-B42D36EF7806@rwa-net.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Jim,
Thanks for your response. Yes the tables have been analysed and I have also re-indexed and vacuumed the slave database.
Regards
Matthew
Sent from my iPad
> On 14 Dec 2015, at 17:49, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
>
>> On 12/14/15 11:16 AM, Matthew Lunnon wrote:
>> Inspecting the execution plan shows that there are some differences, for
>> example, the slave is using a HashAggregate when the master is simply
>> grouping. There also seems to be a difference with the ordering of the
>> sub plans.
>
> Have you tried analyzing the tables on the slave?
>
> Also, keep in mind that the first time you access rows on a Slony slave after they're replicated Postgres will need to write hint bits out, which will take some time. But that's clearly not the issue here.
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
This message has been scanned for malware by Websense. www.websense.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mathieu VINCENT | 2015-12-15 08:05:38 | Re: Estimation row error |
Previous Message | Pedro França | 2015-12-14 20:50:56 | Re: Getting an optimal plan on the first execution of a pl/pgsql function |