Re: [HACKERS] initdb problem

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: emkxp01(at)mtcc(dot)demon(dot)co(dot)uk
Cc: meskes(at)online-club(dot)de, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] initdb problem
Date: 1998-08-27 17:29:53
Message-ID: 199808271729.NAA07671@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
>
> >
> > > On Mon, Aug 24, 1998 at 03:18:28PM -0400, Bruce Momjian wrote:
> > > > Would someone check a running 6.3.2 system and let me know if there are
> > > > any blank attalign values? It think you will find that there are. The
> > > > current patch fixes that.
> > >
> > > echo "select * from pg_attribute where attalign != 'i' and attalign !=
> > > 'c'and attalign != 'd' and attalign!='s';"|psql template1
> >
> > Yikes. Good thing that is fixed now.
> >
>
> Another interesting thing?
>
> (appologies for the width)
>
> I would half expected attalign to be 'd' for all these.
>
> I'm not sure how the values get there though!!

Can you research what the proper value should be. We have char/varchar
set to 'i', but others set to 'd'. What should be the proper value. Is
'd' and 'i' alignment the same on our supported platforms. Does a char
field of length 32 align on int, but a double align on double differently.

--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1998-08-27 20:41:16 Re: AW: TODO (was: Re: [HACKERS] Problem with parser)
Previous Message Bruce Momjian 1998-08-27 17:01:21 Re: AW: TODO (was: Re: [HACKERS] Problem with parser)