| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: is sync rep stalled? |
| Date: | 2010-10-04 07:56:36 |
| Message-ID: | 4CA988B4.4050204@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.10.2010 10:49, Markus Wanner wrote:
> On 10/04/2010 09:18 AM, Heikki Linnakangas wrote:
>> With 'replay' and hot standby combination, you'll want to set
>> max_standby_archive_delay to a very low value, or a read-only query can
>> cause master to stop processing commits (or the standby to stop
>> accepting new queries, if that's preferred).
>
> Well, given that DML-only transactions aren't prone such to conflicts, I
> think of this as a corner case.
Yes they are. Any DML operation, and even read-only queries IIRC, can
trigger HOT pruning, which can conflict with a read-only query in a hot
standby. And then there's autovacuum which can cause conflicts in the
standby, even if no user transactions are running in the master.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2010-10-04 08:17:06 | Re: patch: psql variables tabcomplete |
| Previous Message | Markus Wanner | 2010-10-04 07:49:02 | Re: is sync rep stalled? |