| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: hot standby documentation |
| Date: | 2010-06-23 19:29:54 |
| Message-ID: | 4C2260B2.8040305@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 23/06/10 22:05, Robert Haas wrote:
> On Wed, Jun 23, 2010 at 2:53 PM, Simon Riggs<simon(at)2ndquadrant(dot)com> wrote:
>> We could also allow SELECT ... FOR SHARE during Hot Standby, simply by
>> making it same as normal SELECT, without any ill effects.
>
> True.
Not really. It won't matter while the standby is in read-only mode, but
as soon as the server is promoted to master, you could have other
backends modifying rows that the still-running "SELECT ... FOR SHARED"
transaction should have locked.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2010-06-24 12:23:25 | Re: [DOCS] ECPG Documentation Improvement |
| Previous Message | Robert Haas | 2010-06-23 19:14:41 | Re: hot standby documentation |