Re: Big 7.1 open items

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: 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-16 15:00:35
Message-ID: 7181.961167635@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

JanWieck(at)t-online(dot)de (Jan Wieck) writes:
> There are also disadvantages.

> You can run out of space even if there are plenty GB's
> free on your disks. You have to create tablespaces
> explicitly.

Not to mention the reverse: if I read this right, you have to suck
up your GB's long in advance of actually needing them. That's OK
for a machine that's dedicated to Oracle ... not so OK for smaller
installations, playpens, etc.

I'm not convinced that there's anything fundamentally wrong with
doing storage allocation in Unix files the way we have been.

(At least not when we're sitting atop a well-done filesystem,
which may leave the Linux folk out in the cold ;-).)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Lockhart 2000-06-16 15:11:27 Re: Big 7.1 open items
Previous Message Thomas Lockhart 2000-06-16 14:50:38 Re: Changes to functions and triggers

Browse pgsql-patches by date

  From Date Subject
Next Message Thomas Lockhart 2000-06-16 15:11:27 Re: Big 7.1 open items
Previous Message Tom Lane 2000-06-16 14:22:46 Re: coalesce view error