Search Postgresql Archives

Re: Partitioned tables as a poor mans columnar index?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 16, 2009 at 3:31 PM, marcin mank <marcin.mank@xxxxxxxxx> wrote:
> On Fri, Oct 16, 2009 at 9:19 PM, Peter Hunsberger
> <peter.hunsberger@xxxxxxxxx> wrote:
>
>> The basic problem I have is that I have some tables that are
>> potentially very long (100,000's to millions of rows) and very skinny,
>
>> and I end up with maybe a total of 12 bits of data in each row.
>
> Are You aware that there are some 20-ish bytes of metadata for each
> row? saving 4 bytes buys You nothing. Give it up.

No, the metadata is a whole 'nother problem.  I'm just talking about
fk relationships here.  This isn't an isolated issue within this
particular domain.  If you where to use a conventional table design,
then once the rest of the associated tables get built along with their
associated indexes you'd be looking at in the order of a terabyte for
this half of the DB...

-- 
Peter Hunsberger

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux