Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA48873 for ; Tue, 1 Jun 1999 17:32:32 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id RAA23797; Tue, 1 Jun 1999 17:31:56 -0400 (EDT) To: "Pham, Thinh" cc: "'pgsql-sql@postgresql.org'" Subject: Re: [SQL] Column name's length In-reply-to: Your message of Tue, 1 Jun 1999 11:58:53 -0500 <551413BBBB03D111BF880060B01AACCE0B38F0@home.priority.net> Date: Tue, 01 Jun 1999 17:31:56 -0400 Message-ID: <23795.928272716@sss.pgh.pa.us> From: Tom Lane "Pham, Thinh" writes: >> You will need to do an initdb --- you are making an incompatible change >> in the format of the database. pg_dump with old code, initdb and reload >> with new. > I did all of those and still it gave me that problem. Hmm, that probably means that Zalman hasn't found all the dependencies on NAMEDATALEN after all :-(. Which version are you using, exactly? > I just want to minimize the change > as much as possible w/o touching the frontend. I think you missed the point I made earlier: this sort of change will require a frontend recompile because NAMEDATALEN is visible in frontend apps. regards, tom lane