Re: trigger TOASTing quicker? - Mailing list pgsql-general

From Perez
Subject Re: trigger TOASTing quicker?
Date
Msg-id i-81181E.20401912052006@news.hub.org
Whole thread Raw
In response to trigger TOASTing quicker?  (Perez <i@donotexist.com>)
List pgsql-general
In article <24281.1147444664@sss.pgh.pa.us>,
 tgl@sss.pgh.pa.us (Tom Lane) wrote:

> Martijn van Oosterhout <kleptog@svana.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

pgsql-general by date:

Previous
From: "Chris Coleman"
Date:
Subject: Re: Triggers in C - Segmentation Fault
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Triggers in C - Segmentation Fault