From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
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>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, 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> |
Subject: | RE: Big 7.1 open items |
Date: | 2000-06-21 23:00:17 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A23018C2B@SECTORBASE1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> If we bit the bullet and restricted ourselves to numeric filenames then
> the log would need just four numeric values:
> database OID
> tablespace OID
Is someone going to implement it for 7.1?
> relation OID
> relation version number
I believe that we can avoid versions using WAL...
> (this set of 4 values would also be an smgr file reference token).
> 16 bytes/log entry looks much better than 64.
>
> At the moment I can recall the following opinions:
>
> Pure OID filenames: Thomas, Tom, Marc, Peter E.
+ me.
But what about LOCATIONs? I object using environment and think that
locations
must be stored in pg_control..?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-06-21 23:37:42 | RE: Big 7.1 open items |
Previous Message | Randall Parker | 2000-06-21 22:56:51 | Re: Big 7.1 open items |