From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, zhaoxin <zhaox(at)necas(dot)nec(dot)com(dot)cn>, pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: problem about maximum row size ? |
Date: | 2006-04-12 18:56:33 |
Message-ID: | 200604121856.k3CIuX108667@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Dave Page wrote:
> > > > FAQ updated with new number, and mention that increasing
> > block size
> > > > quadruples it.
> > >
> > > I've updated the limitations page on the website, though I didn't
> > > bother with the blocksize hack on there.
> > >
> > > Whilst we're on the subject, is 16TB for a table still
> > correct given
> > > CE partitioning?
> >
> > Uh, probably not, but do we want to require CE to increase that limit?
>
> It's worth a mention don't you think? Something like:
>
> Maximum table size: 16TB (for a partitioned table, this is the maximum
> size of each partition).
OK, FAQ updated by adding second setence:
<P>The maximum table size, row size, and maximum number of columns
can be quadrupled by increasing the default block size to 32k. The
maximum table size can also be increased using table partitioning.</P>
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Held | 2006-04-12 21:44:13 | ODBC Drivers |
Previous Message | Dave Page | 2006-04-12 18:23:18 | Re: Promoting the enhanced branch |