From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
Subject: | RE: Big 7.1 open items |
Date: | 2000-06-22 01:11:03 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A23018C2D@SECTORBASE1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Giles Lean | 2000-06-22 01:12:54 | Re: An idea on faster CHAR field indexing |
Previous Message | Hiroshi Inoue | 2000-06-22 00:45:46 | RE: Big 7.1 open items |