Re: Big 7.1 open items
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jan Wieck <JanWieck@Yahoo.com>, Tom Lane <tgl@sss.pgh.pa.us>, Hiroshi Inoue <Inoue@tpf.co.jp>, Bruce Momjian <maillist@candle.pha.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>, "Ross J. Reedstrom" <reedstrm@rice.edu>
Date: 2000-06-18T13:33:44Z
Lists: pgsql-hackers
> I haven't figured out extent locations yet. One idea is to allow > administrators to create symlinks for tables >1 gig, and to not remove > the symlinks when a table shrinks. Only remove the file pointed to by > the table, but leave the symlink there so if the table grows again, it > can use the symlink. lstat() would allow this. OK, I have an extent idea. It is: CREATE LOCATION tabloc IN '/var/private/pgsql' EXTENT2 '/usr/pg'. This creates an /extents directory in the location, with extents/2 symlinked to /usr/pg: data/base/mydb/tabloc data/base/mydb/tabloc/extents/2 When extending a table, it looks for an extents/2 directory and uses that if it exists. Same for extents3. We could even get fancy and round-robin through all the extents directories, looping around to the beginning when we run out of them. That sounds nice. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026