From: | Perez <i(at)donotexist(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: trigger TOASTing quicker? |
Date: | 2006-05-13 00:40:23 |
Message-ID: | i-81181E.20401912052006@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In article <24281(dot)1147444664(at)sss(dot)pgh(dot)pa(dot)us>,
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > I beleive you can set it to EXTERNAL, which it will always toast.
>
> I don't think that will help; if the overall row size is below the
> threshold, the code is not going to pick it apart to see if anything
> is saying "toast me anyway!". And it shouldn't do so IMHO; the overall
> cost in cycles would be catastrophic, because most tables aren't going
> to have such columns.
>
> There was discussion just yesterday of making the TOAST thresholds
> more configurable, but I didn't see anyone stepping up with a
> concrete proposal (much less volunteering to create a patch).
>
> regards, tom lane
Well, I suppose I could blank pad the column :-) That would compress
really well, too. Or is that exceptionally evil?
tia,
arturo
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2006-05-13 01:31:43 | Re: GUI Interface |
Previous Message | Bruce Momjian | 2006-05-13 00:38:07 | Re: [GENERAL] Querying libpq compile time options |