> -----Original Message-----
> From: Mikheev, Vadim [mailto:vmikheev(at)SECTORBASE(dot)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 ?
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2000-06-23 05:50:47|
|Subject: Re: PGSQL internals question... |
|Previous:||From: Paul Caskey||Date: 2000-06-23 03:31:59|
|Subject: 64-bit sequences|