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

From Lincoln Yeoh
Subject Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51
Date
Msg-id 3.0.5.32.20010512214116.011f3470@192.228.128.13
Whole thread Raw
In response to Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51  (Peter Eisentraut <peter_e@gmx.net>)
Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 12:35 AM 5/12/01 -0400, Tom Lane wrote:
>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.)

Would n^2-1 or n*8 -1 be better than n^2 or n*8? 

For postgresql it's in the source somewhere, but assuming we can't look,
which would be a better bet? 

Cheerio,
Link.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: Addition to: Trouble with initdb when the #define NAMEDATALEN = 51