Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 78EFE476272 for ; Tue, 30 Apr 2002 14:54:58 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 88AF3475928 for ; Tue, 30 Apr 2002 14:45:54 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3UIjrF21416; Tue, 30 Apr 2002 14:45:53 -0400 (EDT) To: Erik_Erkelens@yahoo.com Cc: pgsql-bugs@postgresql.org Subject: Re: Bug #652: NAMEDATALEN limitations In-reply-to: <21326.1020191577@sss.pgh.pa.us> References: <20020430181519.5E5D9475985@postgresql.org> <21326.1020191577@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Tue, 30 Apr 2002 14:32:57 -0400" Date: Tue, 30 Apr 2002 14:45:53 -0400 Message-ID: <21413.1020192353@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/186 X-Sequence-Number: 3606 I said: > 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. One possible theory is that if NAMEDATALEN isn't a multiple of sizeof(int), the compiler's idea of sizeof(NameData) will probably be NAMEDATALEN rounded up to the next multiple of sizeof(int). However, I still don't see exactly how that breaks anything, with the possible exception of pg_language tuple layout --- but pg_language layout problems wouldn't give rise to a failure during bootstrap AFAICS. So I still don't know what the constraint mechanism really is. BTW, I'm assuming here that alignof(int) is 4 on your platform; is it? regards, tom lane