| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: Creation of temporary tables on read-only standby servers |
| Date: | 2010-10-18 19:26:38 |
| Message-ID: | 24228.1287429998@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On Monday 18 October 2010 20:06:01 Tom Lane wrote:
>> Not unless you have some credible concept for how it might ever be
>> implemented. You can't create temp tables because you can't modify
>> system catalogs, and if you did somehow create them you couldn't put
>> anything in them because you can't generate XIDs on a slave ... much
>> less commit them. We have talked about ways that temp tables might be
>> created without touching the "real" system catalogs, but the XID issue
>> seems a complete showstopper.
> Hm. Wouldnt it be possible to use virtual xids for that purpose? They are
> never seen outside of that session anyway...
Well, maybe, but then you need infrastructure to track whether VXIDs
committed or aborted.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-18 19:29:20 | Re: create tablespace fails silently, or succeeds improperly |
| Previous Message | Jeff Davis | 2010-10-18 19:24:56 | Re: Floating-point timestamps versus Range Types |