From: | Steven Chang <stevenchang1213(at)gmail(dot)com> |
---|---|
To: | gleeco <gleeco(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: is replication effected by exclusive locks? |
Date: | 2017-05-10 07:29:34 |
Message-ID: | CAEJt7k3q+nL+VZJZo1-0=Hf716Z=cMRvzbbmE5B9JUMtS8L48w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
yes if using stream replication due to lock command also being transferred
to slave node
steven
2017-03-26 3:02 GMT+08:00 gleeco <gleeco(at)gmail(dot)com>:
>
> hello - first a thank-you to this list for all previous questions answered
> here!
>
> In our cluster, we're using read-only replicas for answering postgis geo
> queries. Often, i see multiple queries coming in concurrently & regularly
> taking 2-10 seconds. When looking closer at these queries, i see they all
> use an ExclusiveLock.
>
> And when this is the query traffic, there can be increasing replication
> lag.
> But also - there can be waves of tx cancellation due to conflicts, ie.
> replication.
>
> note that in this setup, pg_vacuum_defer_cleanup_age = 0 so the cancels
> make sense to me.
>
> So the simple question: do ExclusiveLock compete or block application of
> wal logs on read replicas?
>
> thanks in advance for thoughts/tips/links/etc
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Brandl, Wolfgang | 2017-05-10 12:24:54 | WG: postgres pg_basebackup |
Previous Message | Klaus P. Pieper | 2017-05-09 10:29:08 | Windows installer initdb with --data-checksums |