Opened 15 years ago

Closed 15 years ago

#4927 closed defect (worksforme)

BUG: initdb fails with PostgreSQL 7.4.8

Reported by: james@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.0
Keywords: Cc:
Port:

Description

I get "ERROR: cache lookup failed for type 1033" when trying to initdb with a fresh install of PostgreSQL 7.4.8. I searched google and can't find anyone else having this problem.

Here is a an example shell session:

# mkdir pgsql # mkdir pgsql/data # chown postgres pgsql/data # su - postgres $ /opt/local/bin/initdb -D /opt/local/var/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 C.

fixing permissions on existing directory /opt/local/var/pgsql/data... ok creating directory /opt/local/var/pgsql/data/base... ok creating directory /opt/local/var/pgsql/data/global... ok creating directory /opt/local/var/pgsql/data/pg_xlog... ok creating directory /opt/local/var/pgsql/data/pg_clog... ok selecting default max_connections... 50 selecting default shared_buffers... 300 creating configuration files... ok creating template1 database in /opt/local/var/pgsql/data/base/1... ERROR: cache lookup failed for type 1033

initdb: failed

If I turn on debugging, there is over one thousand lines of output, but there are the last few:

DEBUG: inserting column 13 value "2275" DEBUG: Typ == NULL, typeindex = 1 DEBUG: -> 2275 DEBUG: inserted DEBUG: inserting column 14 value "2279" DEBUG: Typ == NULL, typeindex = 18 ERROR: cache lookup failed for type 1033 DEBUG: proc_exit(1) DEBUG: shmem_exit(1) DEBUG: exit(1)

initdb: failed

Change History (2)

comment:1 Changed 15 years ago by mww@…

Owner: changed from darwinports-bugs@… to mww@…
Summary: initdb fails with PostgreSQL 7.4.8BUG: initdb fails with PostgreSQL 7.4.8

comment:2 Changed 15 years ago by mww@…

Resolution: worksforme
Status: newclosed

works just fine with 7.4.9 on OS X 10.4; please re-open if problem still exists!

Note: See TracTickets for help on using tickets.