I accidentally wrecked the pg_class table in a database by leaving off
the where clause of an update statement when setting the reltriggers
back to the count from pg_trigger after a bulk data load. I can no
longer connect to the database, although it does start up without
error. running psql
' and relnamespace =
(select oid from pg_namespace where nspname = '$sch')))--should have
been a limiting where clause here
Thanks,
Roger
Tom Lane wrote:
Roger Ging <[EMAIL PROTECTED]> writes:
I accidentally wrecked the pg_class table in a database by leaving off
the
Tom,
Thanks for the info. I have begun the rebuild from backups. The
machine is a data warehouse with no backups of it's own, but all of
the data is available from other servers.
Roger
Tom Lane wrote:
Roger Ging <[EMAIL PROTECTED]> writes:
update pg_class set
The pg version is 8.3.1 running on Suse. Hardware is 2X dual core
Opterons, 16 GB RAM, 24 drives in RAID 50
It would seem to me that the system is extremely IO bound, but I don't
know how to find out what specifically is wrong here. Any advice
greatly appreciated.
--
Roger Ging
--
to upgrade versions. I am taking it offline this
weekend and will install the latest. I'll try to re-create the
scenario I had going on yesterday over the weekend and get some io
statistics.
Roger
Scott Marlowe wrote:
On Fri, Feb 13, 2009 at 10:20 AM, Roger Ging wrote:
Hi,
