Re: Bug #652: NAMEDATALEN limitations - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug #652: NAMEDATALEN limitations
Date
Msg-id 21326.1020191577@sss.pgh.pa.us
Whole thread Raw
In response to Bug #652: NAMEDATALEN limitations  (pgsql-bugs@postgresql.org)
Responses Re: Bug #652: NAMEDATALEN limitations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
pgsql-bugs@postgresql.org writes:
> If NAMEDATALEN is given values of 45,61 initdb -d  will fail with the error "relation pg_proc does not exist'.

Did you try to track down why?

Although it's inefficient to declare NAMEDATALEN as not a multiple of 4
(because of alignment considerations --- the space will just be wasted
as pad bytes, so you might as well use it), I don't offhand know why it
wouldn't work.  I don't *think* there is any assumption that it's a
power of 2 ... but the well-tested cases are all powers of 2, so ...

> I'd appreciate a comment in e.g. postgress_ext.h telling me e.g. that it should be a power of two, even or something
likethat. 

To do that, we'd need to know what the constraint actually is.  Do you
care enough to do the research to find out?

From my perspective it'd be even better to remove whatever the
constraint is, if it turns out to be a localized fix.  But not knowing
what's causing the failure, it's hard to guess.

            regards, tom lane

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #652: NAMEDATALEN limitations
Next
From: Tom Lane
Date:
Subject: Re: Bug #652: NAMEDATALEN limitations