RE: Big 7.1 open items - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject RE: Big 7.1 open items
Date
Msg-id 000101bfdcc6$13b186a0$2801007e@tpf.co.jp
Whole thread Raw
In response to RE: Big 7.1 open items  ("Mikheev, Vadim" <vmikheev@SECTORBASE.COM>)
List pgsql-hackers
> -----Original Message-----
> From: Mikheev, Vadim [mailto:vmikheev@SECTORBASE.COM]
> 
> > > I believe that we can avoid versions using WAL...
> > 
> > I don't think so.  You're basically saying that
> >     1. create file 'new'
> >     2. delete file 'old'
> >     3. rename 'new' to 'old'
> > is safe as long as you have a redo log to ensure that the rename
> > happens even if you crash between steps 2 and 3.  But crash is not
> > the only hazard.  What if step 3 just plain fails?  Redo won't help.
> 
> Ok, ok. Let's use *unique* file name for each table version.
> But after thinking, seems that I agreed with Hiroshi about using
> *some unique id* for file names instead of oid+version: we could use
> just DB' OID + this unique ID in log records to find table file - just
> 8 bytes.
> 
> So, add me to Hiroshi' camp... if Hiroshi is ready to implement new file
> naming -:)
>

I've thought e.g. newfileid() like newoid() using pg_variable.
Other smarter ways ? 

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp


pgsql-hackers by date:

Previous
From: Paul Caskey
Date:
Subject: 64-bit sequences
Next
From: Tom Lane
Date:
Subject: Re: PGSQL internals question...