Any risk in increasing BLCKSZ to get larger tuples?

From: Philip Hallstrom <philip(at)adhesivemedia(dot)com>
To: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Any risk in increasing BLCKSZ to get larger tuples?
Date: 2000-10-18 21:46:36
Message-ID: Pine.BSF.4.21.0010181444450.39346-100000@oddjob.adhesivemedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi -
I'm thinking about using postgres for an app that will store
various email messages which might (although probably not likely) be
larger than the builtin limit for tuples. Is there anything I should be
aware of before changing the below value and recompiling?

Also, it looks like the TOAST stuff would solve this (right/wrong?), but
it's not going to be ready for 7.1 (right/wrong?)

Thanks!

from src/include/config.h
/*
* Size of a disk block --- currently, this limits the size of a tuple.
* You can set it bigger if you need bigger tuples.
*/
/* currently must be <= 32k bjm */
#define BLCKSZ 8192

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nate Lawson 2000-10-18 22:11:12 MySQL PASSWORD('x') function workalike
Previous Message Neil Conway 2000-10-18 20:54:06 rules *very* slow?