Skip site navigation (1) Skip section navigation (2)

Re: Significantly larger toast tables on 8.4?

From: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
To: Alex Hunsaker <badalex(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Significantly larger toast tables on 8.4?
Date: 2009-01-02 20:23:13
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Alex Hunsaker wrote:
>I think we could just add another toast storage type: alter table
>alter column set storage compress; ?  It seems overkill to expose
>PGLZ_Strategy knobs per column...

Three things:
a. Shouldn't it in theory be possible to have a decompression algorithm
   which is IO-bound because it decompresses faster than the disk can
   supply the data?  (On common current hardware).
b. Has the current algorithm been carefully benchmarked and/or optimised
   and/or chosen to fit the IO-bound target as close as possible?
c. Are there any well-known pitfalls/objections which would prevent me from
   changing the algorithm to something more efficient (read: IO-bound)?
           Stephen R. van den Berg.

"Always remember that you are unique.  Just like everyone else."

In response to


pgsql-hackers by date

Next:From: Robert HaasDate: 2009-01-02 20:35:18
Subject: Re: Significantly larger toast tables on 8.4?
Previous:From: Tom LaneDate: 2009-01-02 20:01:45
Subject: Re: posix_fadvise v22

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group