Postgres Pro
Downloads
Home   >   mailing lists

Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51
Date
Msg-id 8391.989642138@sss.pgh.pa.us
Whole thread Raw
In response to Addition to: Trouble with initdb when the #define NAMEDATALEN = 51  ("G. Anthony Reina" <reina@nsi.edu>)
Responses Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
List pgsql-hackers
Tree view 
"G. Anthony Reina" <reina@nsi.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

pgsql-hackers by date:

Previous
From: Thomas Lockhart
Date:
Subject: Re: Rtree on custom data types; type conversion stops index use.
Next
From: Lincoln Yeoh
Date:
Subject: Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51