Re: Summary and Plan for Hot Standby - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: Summary and Plan for Hot Standby
Date
Msg-id 20091116.190627.108810018.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Re: Summary and Plan for Hot Standby  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Summary and Plan for Hot Standby
List pgsql-hackers
> > - 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?

> > - Can we create tempory tables in standby?
> 
> No, but this is for two reasons
> 
> * CREATE TEMPORARY TABLE actually writes to catalog tables. It doesn't
> need to do that, so allowing this would require some medium-heavy
> lifting of the way temp tables work. A preliminary design was agreed in
> July 2008. I believe it would be a popular feature, since about 40-50%
> of people ask for this.
> 
> * CREATE TEMP TABLE is currently considered to be disallowed during read
> only transactions. That might be able to change if the underlying
> physical operation were write-free.

Thanks for explanation.
--
Tatsuo Ishii
SRA OSS, Inc. Japan


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: patch - per-tablespace random_page_cost/seq_page_cost
Next
From: "Albe Laurenz"
Date:
Subject: Re: TRIGGER with WHEN clause