Bug #60469: reported problem on PowerPC with PostgreSQL
Georg Bauer <gb@hugo.westfalen.de> reported the following bug, which I
cannot reproduce on Intel architecture:
============================================================================
Title: typeidTypeRelid: Invalid type - oid = 0 when trying to look at tables
Package: postgresql
Version: 6.5.3-12
Severity: important
All commands that try to work on table parameters don't work because of the
given error message. If I do the following:
\d pg_class
I get the mentioned error message. This occurs always when the oid of a table
is
accessed, as it seems. This for example breaks the code that lists available
tables
in pgaccess.
bye, Georg
-- System Information
Debian Release: 2.2
Architecture: powerpc
Kernel: Linux jill 2.2.13ext3 #1 Die Mär 7 23:33:24 CET 2000 ppc
Versions of packages postgresql depends on:
ii debianutils 1.13.2 Miscellaneous utilities specific t
ii libc6 2.1.3-2 GNU C Library: Shared libraries an
ii libncurses5 5.0-5 Shared libraries for terminal hand
ii libpgsql2 6.5.3-12 Shared library libpq.so.2 for Post
ii libreadline4 4.1-0beta5db1 GNU readline and history libraries
ii postgresql-client 6.5.3-12 Front-end programs for PostgreSQL
ii procps 1:2.0.6-5 The /proc file system utilities.
-- Configuration Files:
/etc/postgresql/postmaster.init changed:
POSTGRES_HOME=`grep '^postgres:' /etc/passwd | awk -F: '{print $6}' | head -1`
if [ -z "$POSTGRES_HOME" ]
then
POSTGRES_HOME=/var/lib/postgres
fi
PGDATESTYLE=GERMAN
PGALLOWTCPIP=yes
============================================================================
Has any other PowerPC user experienced this, please?
--
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"Bless them which persecute you; bless, and curse not.
Rejoice with them that do rejoice, and weep with them
that weep. Recompense to no man evil for evil. Provide
things honest in the sight of all men."
Romans 12:14,15,17
Reply to: