[HACKERS] cvs 'initdb' -- vacuuming database template1 ... FATAL: could not identify a comparison function for type aclitem

2006-11-06 Thread Matt Miller
head does this to me when I try to initdb:

[EMAIL PROTECTED]:~$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
The files belonging to this database system will be owned by user postgres.
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

fixing permissions on existing directory /usr/local/pgsql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in /usr/local/pgsql/data/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... FATAL:  could not identify a comparison 
function for type aclitem
child process exited with exit code 1
initdb: removing contents of data directory /usr/local/pgsql/data

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] cvs 'initdb' -- vacuuming database template1 ... FATAL: could not identify a comparison function for type aclitem

2006-11-06 Thread Tom Lane
Matt Miller [EMAIL PROTECTED] writes:
 head does this to me when I try to initdb:

I bet you didn't do a full recompile after cvs update.
If you're not using --enable-depend then you really have
to do make clean or even make distclean.

regards, tom lane

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster