pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Erik_Erkelens@yahoo.com
Cc: pgsql-bugs@postgresql.org
Subject: Re: Bug #652: NAMEDATALEN limitations
Date: Tue, 30 Apr 2002 14:45:53 -0400
Message-ID: <21413.1020192353@sss.pgh.pa.us> (raw)
In-Reply-To: <21326.1020191577@sss.pgh.pa.us>
References: <20020430181519.5E5D9475985@postgresql.org>
	<21326.1020191577@sss.pgh.pa.us>

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



view thread (4+ messages)  latest in thread

Message-ID: <21413.1020192353@sss.pgh.pa.us>
Permalink:  ../21413.1020192353@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21413.1020192353@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Erik_Erkelens@yahoo.com, pgsql-bugs@postgresql.org
  Subject: Re: Bug #652: NAMEDATALEN limitations
  In-Reply-To: <21413.1020192353@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox