Received: from home.priority.net (home.priority.net [204.27.108.182]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA64123 for ; Tue, 1 Jun 1999 09:09:31 -0400 (EDT) (envelope-from tpham@mail.priority.net) Received: by home.priority.net with Internet Mail Service (5.5.2232.9) id ; Tue, 1 Jun 1999 08:25:32 -0500 Message-ID: <551413BBBB03D111BF880060B01AACCE0B38EE@home.priority.net> From: "Pham, Thinh" To: pgsql-sql@postgreSQL.org Subject: RE: [SQL] Column name's length Date: Tue, 1 Jun 1999 08:25:31 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Is there any reason you made OIDNAMELEN 260 instead of 256? Also, should i wait until 6.5 came out before trying to fix this thing? Since it looks like it's not going to be fixed in 6.5 either. I don't want to dump/reload this thing too many times since it stores a lot of other more critical data besides this timeclock thing. I saw the postgres website mentioned that 6.5 is coming out in around one week, is that true? Thinh > ----- > diff postgresql-6.4.2/src/include/postgres_ext.h > postgres-build/src/include/postgres_ext.h > 34c34 > < #define NAMEDATALEN 32 > --- > > #define NAMEDATALEN 256 > 37c37 > < #define OIDNAMELEN 36 > --- > > #define OIDNAMELEN 260 > ----- > diff postgresql-6.4.2/src/include/storage/buf_internals.h > postgres-build/src/include/storage/buf_internals.h > 87c87 > < #define PADDED_SBUFDESC_SIZE 128 > --- > > #define PADDED_SBUFDESC_SIZE 1024 > -----