AW: File versioning (was: Big 7.1 open items)

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Hiroshi Inoue'" <Inoue(at)seiren(dot)co(dot)jp>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>
Subject: AW: File versioning (was: Big 7.1 open items)
Date: 2000-06-26 10:54:11
Message-ID: 219F68D65015D011A8E000006F8590C605BA5992@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hiroshi Inoue [mailto:Inoue(at)seiren(dot)co(dot)jp] wrote:
> > > Besides which, OID alone doesn't give us a possibility of file
> > > versioning, and as I commented to Vadim I think we will want that,
> > > WAL or no WAL. So it seems to me the two viable choices are
> > > unique-id or OID+version-number. Either way, the
> file-naming behavior
> > > should be the same across all platforms.
> >
> > I do not think the only problem of a failing rename of
> "temp" to "new"
> > on startup rollforward is issue enough to justify the additional
> > complexity
> > a version implys.
>
> Hmm,I've always mentioned about usual rollback and never mentioned
> about rollforward on this topic AFAIR. Could you tell me what you mean
> by * on startup rollforward* ?

situation:
$ alter table ...

db crash before rename is done but rest was ok.

$ startup

rollforward tx log which has the open entry for the rename table

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yutaka tanida 2000-06-26 11:33:11 Re: [HACKERS] .exe extension on Windows
Previous Message Zeugswetter Andreas SB 2000-06-26 10:50:10 AW: Big 7.1 open items