From: | Steven Schlansker <steven(at)likeness(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Ignore hash indices on replicas |
Date: | 2012-08-20 17:26:03 |
Message-ID: | EC640C6C-74F4-40CF-8CFD-1836AF506F87@likeness.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Aug 19, 2012, at 8:01 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Tue, Jul 10, 2012 at 1:09 AM, Steven Schlansker <steven(at)likeness(dot)com> wrote:
>> I'm using Postgres hash indices on a streaming replica master.
>> As is documented, hash indices are not logged, so the replica does not have access to them.
>>
>> I understand that the current wisdom is "don't use hash indices", but (unfortunately?) I have benchmarks that
>> show that our particular application is faster by quite a bit when a hash index is available.
>
> You could use a slony slave and have different indexes etc between
> master and slave but it's more complex to setup, maintain and monitor
> for most people.
Thanks for the suggestion, but we finally have replication working in a way we understand / like and I don't really consider this a viable option. The built-in replication has been treating us very well.
From | Date | Subject | |
---|---|---|---|
Next Message | Steven Schlansker | 2012-08-20 17:29:33 | Re: Ignore hash indices on replicas |
Previous Message | Sebastien Boisvert | 2012-08-20 16:52:41 | postmaster.pid file auto-clean up? |