From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Hot Standby Query Conflicts |
Date: | 2009-01-06 15:01:40 |
Message-ID: | 1231254100.15005.45.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
After various discussions over last few months, it's now time to
finalise the way we handle query conflicts in Hot Standby.
Please can interested people read
http://wiki.postgresql.org/wiki/Hot_Standby#Query_Conflicts
which is user docs for how HS will handle this. Remember we're nearly in
beta, so this is really just to check understanding rather than to
generate further ideas and debate.
The whole of http://wiki.postgresql.org/wiki/Hot_Standby#Usage
is also worth reading, which now runs to about 4-5 pages/screens.
Design overview stuff is somewhat historical now, but may be interesting
to read since it continues earlier design thoughts.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-01-06 15:11:18 | Re: Is there a way to do an exact-match search on this list? |
Previous Message | Robert Haas | 2009-01-06 14:57:10 | Re: QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows) |