Well that's odd, since 7.2 has a pg_user table. hrm...

On Wed, 2 Jul 2003, S.Peppe wrote:


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

"scott.marlowe" <scott.marlowe (AT) ihs (DOT) com> writes:
Well, it's a view actually, and the backend would continue to run just
fine if someone were to drop or rename the view. psql has some built-in
queries that expect it to be there though.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

OK, here's what I did...

I manually deleted the contents of the /var/lib/postgres directory, did
a dpkg -P postgresql and/or aptitude remove postgresql postgresql-client
to uninstall postgresql (yes, the server is running Debian), deleted
/var/lib/postgres between uninstalling and reinstalling postgresql
(checked that /var/lib/postgres was indeed gone), and reinstalled
postgresql and postgresql-client.

Heavy-handed? Yes, but I couldn't find a solution, and I couldn't
afford to wait any longer. Shame really, but it now seems to
work. Thanks to everyone for offering their suggestions. All the very
best to you!

Regards,

Sam.

On Wed, 2 Jul 2003, scott.marlowe wrote:


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