> Have you looked at the below?:
>
> http://www.postgresql.org/docs/9.2/interactive/hot-standby.html#HOT-STANDBY-CONFLICT
>
> 25.5.2. Handling Query Conflicts
Yes, thank you!
I am hoping to hear more from people who have running 9.2 systems w/ between 100m and 1b records, w/ streaming
replicationand heavy data mining on the slaves (5-50m records read per hour by multiple parallel processes), while from
timeto time (2-3 times/week) between 20 and 50m records are inserted/updated within 24 hours.
How do they resolve this situation.
For us retry + switch slave works quite well right now, without touching the db configuration in this respect yet.
But may be there are different approaches.