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

From Mikheev, Vadim
Subject RE: Big 7.1 open items
Date
Msg-id 8F4C99C66D04D4118F580090272A7A23018C2F@SECTORBASE1
Whole thread Raw
In response to Big 7.1 open items  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses RE: Big 7.1 open items  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Re: Big 7.1 open items  (Giles Lean <giles@nemeton.com.au>)
List pgsql-hackers
> > > > Or - create tmp file and load with new content;
> > > > log "intent to relink table file";
> > > > relink table file; log "file is relinked".
> > > 
> > > It seems to me that whole content of the table should be
> > > logged before relinking or shrinking.
> > 
> > Why not just fsync tmp files?
> >
> 
> Probably I've misunderstood *relink*.
> If *relink* different from *rename* ?

I ment something like this - link(table file, tmp2 file); fsync(tmp2 file);
unlink(table file); link(tmp file, table file); fsync(table file);
unlink(tmp file). We can do additional logging (with log flush) of these
steps
if required, postpone on-recovery redo of operations till last relink log
record/
end of log/transaction abort etc etc etc.

Vadim


pgsql-hackers by date:

Previous
From: "Hiroshi Inoue"
Date:
Subject: RE: Big 7.1 open items
Next
From: "Randall Parker"
Date:
Subject: Re: An idea on faster CHAR field indexing