| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Klaus Naumann <lists(at)distinctmind(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Constant WAL replay |
| Date: | 2005-04-24 15:41:17 |
| Message-ID: | 6192.1114357277@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Klaus Naumann <lists(at)distinctmind(dot)de> writes:
>> what. Allowing that to be turned off would be interesting for a number
>> of purposes, such as burning a database onto CD.
> FWIW, Oracle suggests a "transportable tablespace" for this feature.
> Which is a tablespace that is not written too and which can be read by
> any database.
> Would that solve the purposes you mean?
It's a very long way from here to there. In particular, since different
installations have different transaction histories, the XIDs in the
table could not be transportable. You'd almost be forced to build
something like the non-MVCC, XID-less table type that was being
speculated about up-thread.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-24 16:01:01 | Re: [HACKERS] UNICODE/UTF-8 on win32 |
| Previous Message | John Hansen | 2005-04-24 14:09:08 | Re: [HACKERS] UNICODE/UTF-8 on win32 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-04-24 17:07:13 | Re: Constant WAL replay |
| Previous Message | Tom Lane | 2005-04-24 15:33:53 | Re: Minor Comment updates |