Jeff Davis <jdavis-pgsql(at)empires(dot)org> writes:

> But of course, we all love toast. Everyone needs to make those wide
> tables once in a while, and toast does a great job of taking those
> worries away in an efficient way. I am just saying that hopefully we
> don't have to seqscan a table with wide tuples very often :)

I thought toast only handled having individual large columns. So if I have a
2kb text column it'll pull that out of the table for me. But if I have 20
columns each of which have 100 bytes will it still help me? Will it kick in if
I define a single column which stores a record type with 20 columns each of
which have a 100 byte string?

-- 
greg

In response to

• Re: Much Ado About COUNT(*) at 2005-01-13 02:45:09 from Jeff Davis

Responses

• Re: Much Ado About COUNT(*) at 2005-01-13 03:50:57 from Tom Lane

pgsql-announce by date

Next:	From: Tom Lane	Date: 2005-01-13 03:50:57
	Subject: Re: Much Ado About COUNT(*)
Previous:	From: Jeff Davis	Date: 2005-01-13 02:45:09
	Subject: Re: Much Ado About COUNT(*)

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2005-01-13 03:50:57
	Subject: Re: Much Ado About COUNT(*)
Previous:	From: Jeff Davis	Date: 2005-01-13 02:45:09
	Subject: Re: Much Ado About COUNT(*)

pgsql-patches by date

Next:	From: Tom Lane	Date: 2005-01-13 03:50:57
	Subject: Re: Much Ado About COUNT(*)
Previous:	From: Jeff Davis	Date: 2005-01-13 02:45:09
	Subject: Re: Much Ado About COUNT(*)