Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Constant WAL replay


  • From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Klaus Naumann <lists(at)distinctmind(dot)de>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: Constant WAL replay
  • Date: Sun, 24 Apr 2005 13:07:13 -0400
  • Message-id: <20050424170713(dot)GB24170(at)dcc(dot)uchile(dot)cl>

On Sun, Apr 24, 2005 at 11:41:17AM -0400, Tom Lane wrote:
> 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.

Unless the tables are frozen first.

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"En las profundidades de nuestro inconsciente hay una obsesiva necesidad
de un universo lógico y coherente. Pero el universo real se halla siempre
un paso más allá de la lógica" (Irulan)



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group