Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "G(dot) Anthony Reina" <reina(at)nsi(dot)edu>
Cc: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51
Date: 2001-05-12 04:35:38
Message-ID: 8391.989642138@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"G. Anthony Reina" <reina(at)nsi(dot)edu> writes:
>> In postgres_ext.h, I changed:
>>
>> #define NAMEDATALEN 32
>> to
>> #define NAMEDATALEN 51
>>
>> Everything compiled and installed. However, the initdb started up but
>> then just said that it failed.

I have not tried that in awhile, but the last time I did, it worked
fine. Are you sure you did a *complete* rebuild? I'd suggest make
distclean at the top level, configure, make all, install, initdb.

BTW, 51 is a gratuitously wasteful setting --- given alignment
considerations, any value that's not a multiple of 4 is pointless.
(It should work ... but it's pointless.)

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Kreen 2001-05-12 08:51:29 Re: bug in pgcrypto 0.3
Previous Message Thomas Lockhart 2001-05-12 04:09:07 Re: Rtree on custom data types; type conversion stops index use.