Re: Bad plan on a view - Mailing list pgsql-performance

From PFC
Subject Re: Bad plan on a view
Date
Msg-id op.s5qrbf17cigqcu@apollo13
Whole thread Raw
In response to Re: Bad plan on a view  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bad plan on a view  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-performance
> Aren't you going to a lot of work to reinvent something that TOAST
> already does for you?  (At least, in the cases where the text fields
> are wide enough that it really matters.)

    I know. But I have several text fields in the 20 to 200 characters, which
is too small for toast, but large enough to make up about 90% of the table
size, which makes it problematic RAM-wise, especially since it's gonna
grow. Now, if I had 1 big text field, it would be TOASTed and I would be
happy ;)


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bad plan on a view
Next
From: Greg Stark
Date:
Subject: Re: Bad plan on a view