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-18T14:35:54Z
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'. Even better: CREATE LOCATION tabloc IN '/var/private/pgsql' EXTENT '/usr/pg', '/usr1/pg' This will create extent/2 and extent/3, and the system can rotate extents between the primary storage area, and 2 and 3. Also, CREATE INDEX will need a location specification added. -- 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