From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org, heikki(dot)linnakangas(at)enterprisedb(dot)com |
Subject: | Re: Summary and Plan for Hot Standby |
Date: | 2009-11-16 17:13:13 |
Message-ID: | 1258391593.14054.4826.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2009-11-16 at 19:06 +0900, Tatsuo Ishii wrote:
> > > - Does Hot Standby allow to use prepared query (not prepared
> > > transaction) in standby? I mean: Parse message from frontend can be
> > > accepted by standby?
> >
> > Yes, no problem with any of those kind of facilities
>
> Please correct me if I'm wrong. Parse will result in obtaining
> RowExclusiveLock on the target table if it is parsing
> INSERT/UPDATE/DELETE. If so, is this ok in the standby?
Any attempt to take RowExclusiveLock will fail.
Any attempt to execute INSERT/UPDATE/DELETE will fail.
This behaviour should be identical to read only transaction mode. If it
is not documented as an exception, please report as a bug.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2009-11-16 17:17:55 | Re: next CommitFest |
Previous Message | Peter Eisentraut | 2009-11-16 17:05:10 | Re: [HACKERS] pgsql: /home/peter/commit-msg |