Re: AW: File versioning (was: Big 7.1 open items) - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: AW: File versioning (was: Big 7.1 open items)
Date
Msg-id 3957E7F2.2F9AA64D@tpf.co.jp
Whole thread Raw
In response to AW: File versioning (was: Big 7.1 open items)  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
List pgsql-hackers
Zeugswetter Andreas SB wrote:

> Hiroshi Inoue [mailto:Inoue@seiren.co.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
>

Doesn't above *startup* mean the startup of transaction recovery ?
Because I don't know Vadim's implementation about WAL well,I've
never taken WAL into account in this topic.  I've always discussed
about usual rollback and so the problem you've pointed out is not
my point of discussion.
Seems we have discussed this topic from different POV.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp




pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: .exe extension on Windows
Next
From: Ryan Kirkpatrick
Date:
Subject: Re: Re: Call for port testing on fmgr changes -- Results!