On Fri, Jun 20, 2008 at 2:58 PM, Bill Ott <[EMAIL PROTECTED]> wrote: > >> The second one will take a while, and it is possible for it to fail if >> there are records with fields greater than 2.7k and Postgres was not >> adjusted at compile time to increase the page size. >> >> > > Doh! > > ERROR: index row size 4232 exceeds btree maximum, 2713 > HINT: Values larger than 1/3 of a buffer page cannot be indexed. > Consider a function index of an MD5 hash of the value, or use full text > indexing. > > > I believe you noted to me previously that this requires an initdb after the > recompile? >
Indeed. The on-disk format will be different Attached is a patch for Postgres 8.2.9, but it should apply to any version without any trouble. -- Mike Rylander | VP, Research and Design | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [EMAIL PROTECTED] | web: http://www.esilibrary.com
diff -pu postgresql-8.2.9/src/include/pg_config_manual.h postgresql-8.2.9-patch/src/include/pg_config_manual.h --- postgresql-8.2.9/src/include/pg_config_manual.h 2006-09-18 18:40:40.000000000 -0400 +++ postgresql-8.2.9-patch/src/include/pg_config_manual.h 2008-06-20 15:10:06.000000000 -0400 @@ -23,7 +23,7 @@ * * Changing BLCKSZ requires an initdb. */ -#define BLCKSZ 8192 +#define BLCKSZ 32768 /* * RELSEG_SIZE is the maximum number of blocks allowed in one disk
