From: | Laurent Laborde <kerdezixe(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | jd(at)commandprompt(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Higher TOAST compression. |
Date: | 2009-07-20 08:17:18 |
Message-ID: | 8a1bfe660907200117p2f291864wd06056efe753afcf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 17, 2009 at 11:10 PM, Kevin
Grittner<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Laurent Laborde <kerdezixe(at)gmail(dot)com> wrote:
>
>> What about SET STORAGE MAIN then ? To prevent out-of-line storage ?
>
> Well, that doesn't try as hard as you might think to keep from storing
> data out-of-line. It uses the same threshold as the default EXTENDED
> storage, but saves the out-of-line option for such columns as the last
> thing to try to get it within the threshold. It is because I wrote a
> very small patch to address that issue that I jumped in on your issue.
>
> If you wanted to try my patch here:
>
> http://archives.postgresql.org/message-id/4A3638530200002500027A95@gw.wicourts.gov
>
> you could adjust both TOAST_TUPLES_PER_PAGE_MAIN and
> TOAST_TUPLES_PER_PAGE to suit your needs and set storage for columns
> to MAIN as needed. Be very cautious if you try this, because this
> patch has not yet been reviewed or accepted.
I'll take a look at it, compile, and try that. (on a test server).
Thank you :)
--
Laurent Laborde
Sysadmin @ http://www.over-blog.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2009-07-20 11:11:23 | Re: WIP: Deferrable unique constraints |
Previous Message | Jeremy Kerr | 2009-07-20 07:14:02 | Re: [PATCH 1/2 v3] [libpq] rework sigpipe-handling macros |