Re: Any risk in increasing BLCKSZ to get larger tuples?

[stuff about why 7.1 isn't out and the 8K limit and TOAST AND WAL snipped]

> And do you really think that WAL is more important that TOAST? I
> imagine a good percentage of users bump up against the 8K limit and end
> up with corrupted data (like I did) but much fewer think that WAL is a
> critical feature.

If I had to pick I would rather have WAL over TOAST. I originally asked
the question about BLCKSZ and this is the first app that I am worried
about hitting that limit. It's actually never even crossed my mind before
this since usually if it's big it's an image and I just store it on disk
with a filename in the database. And I would say for a lot of web uses 8K
(or the 32K max) is way more than adequate.
WAL on the other hand would be really nice because even if my data
is small, it sure would be nice to reproduce it in the case of a monstrous
crash.

just my 2 cents.

-philip