Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA84176 for ; Tue, 1 Jun 1999 11:01:39 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id KAA25262; Tue, 1 Jun 1999 10:42:02 -0400 (EDT) From: Bruce Momjian Message-Id: <199906011442.KAA25262@candle.pha.pa.us> Subject: Re: [SQL] Column name's length In-Reply-To: <551413BBBB03D111BF880060B01AACCE0B38EE@home.priority.net> from "Pham, Thinh" at "Jun 1, 1999 08:25:31 am" To: "Pham, Thinh" Date: Tue, 1 Jun 1999 10:42:02 -0400 (EDT) CC: pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit [Charset iso-8859-1 unsupported, filtering to ASCII...] > 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 It has to be 260 if NAMEDATALEN is 256: /* OIDNAMELEN should be set to NAMEDATALEN + sizeof(Oid) */ #define OIDNAMELEN 36 6.5 is scheduled for June 7. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026