Re: Maximum table size

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Maximum table size
Date: 2003-09-09 13:27:21
Message-ID: Pine.LNX.4.33.0309090727110.13569-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 9 Sep 2003, Tom Lane wrote:

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Is our maximum table size limited by the maximum block number?
>
> Certainly.
>
> > Is the 16TB number a hold-over from when we weren't sure block number
> > was unsigned, though now we are pretty sure it is handled as unsigned
> > consistenly?
>
> It's a holdover. As to how certain we are that all the
> signed-vs-unsigned bugs are fixed, who have you heard from running a
> greater-than-16Tb table? And how often have they done CLUSTER, REINDEX,
> or even VACUUM FULL on it? AFAIK we have zero field experience to
> justify promising that it works.
>
> We can surely fix any such bugs that get reported, but we haven't got
> any infrastructure that would find or prevent 'em.

any chance OSDL could test it?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-09-09 13:40:27 Re: [PATCHES] mcxt.c
Previous Message scott.marlowe 2003-09-09 13:13:56 Re: undefine currval()