Re: [INTERFACES] Postgres Limitations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter T Mount <peter(at)retep(dot)org(dot)uk>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] Postgres Limitations
Date: 1999-02-05 17:36:48
Message-ID: 18150.918236208@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[ Redirected to hackers, as it's now way off-topic for pgsql-interfaces ]

Peter T Mount <peter(at)retep(dot)org(dot)uk> writes:
> [ trying to test whether Postgres can split a huge database into
> multiple 2-Gb files ]
> The problem I have is that it takes 4 hours for a table to reach 2Gb on my
> system, so it's a slow process :-(

I had a thought about this --- is there a #define somewhere that sets
the size at which the system decides it needs to split a table?
(If not, shouldn't there be?) If there is, you could build a debug
copy of Postgres in which the value is set very small, maybe a meg or
less, and then it'd be easy to test the file-splitting behavior.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-02-05 17:48:05 Re: postgres bug?
Previous Message Bruce Momjian 1999-02-05 17:24:28 Re: [HACKERS] DEC OSF1 Compilation problems