Re: [HACKERS] initdb problem

> On Tue, Aug 25, 1998 at 12:53:21AM -0400, Bruce Momjian wrote:
> > OK. I did a little checking:
> >
> > #$ cd /pg/include/catalog/
> > #$ grep 683 *.h
> > #$ grep 682 *.h
> > #$ grep 681 *.h
> > pg_proc.h:DATA(insert OID = 681 ( oid8gt PGUID
> > 11 f t f 2 f 16 "30 30" 100 0 0 100 foo bar ));
>
> Exactly the same results for me.
>
> > #$ sql test
> > seleWelcome to the POSTGRESQL interactive sql monitor:
> > Please read the file COPYRIGHT for copyright terms of POSTGRESQL
> >
> > type \? for help on slash commands
> > type \q to quit
> > type \g or terminate with semicolon to execute query
> > You are currently connected to the database: test
> >
> > ctest=> select * from pg_proc where oid = 683
> > test-> \g
> > proname|proowner|prolang|proisinh|proistrusted|proiscachable|pronargs|proretset|prorettype|proargtypes|probyte_pct|properbyte_cpu|propercall_cpu|prooutin_ratio|prosrc|probin
> > -------+--------+-------+--------+------------+-------------+--------+---------+----------+-----------+-----------+--------------+--------------+--------------+------+------
> > (0 rows)
>
> Cannot check that since it is initdb that fails.
>
> > that somewhere you have something with that number in your source, and
> > it should not be there.
>
> I grep through the whole source tree and all I found is:
>
> #define F_OID8EQ 683
>
> in ./include/fmgr.h

That is the problem. I don't have an fmgr.h file in include, just in
backend/fmgr.h. It is finding an old one first. It was not a problem
as long as no one made changes to the system tables, but I did.

That is why the clean cvsup worked for people. How the fmgr.h file got
into include, I have no idea.

The only 683 I get from the source are labels in gram.c.

Remove the file and recompile.

--
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)