From: | Thomas Seeber <thomas(dot)seeber(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Wierd Error on update |
Date: | 2004-08-13 16:21:53 |
Message-ID: | 578aa3f704081309222548a2e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> Original 7.3 release, or (I hope) 7.3.something?
Red Hat 7.3.2.96-113
Linux Version 2.4.20-20.7custom from cat /proc/version
> > I am getting two errors which are a bit confounding.
> > ERROR: pg_class_aclcheck:relation 474653086 not found
>
> Are there any views involved?
No views.
Is the statement invoking any functions?
The statement is not invoking any fuctions
However heres the statements,
UPDATE school_info_l SET ind_default_data = 't';
UPDATE school_info_l SET sis_system_id = 9 where school_id IN (492, 434, 436);
which are amazingly simple.
Both queries return the same exact error, same error.
not your
> How about triggers? Foreign keys? Rules?
Neither of the updates touch any rules.
sis_system_id has a foreign key constaint to another table that does
in it contain a value of 9 for sis_system_id in that table, but the
first isnt touching anything that has a trigger or foreign key
constraint attached to the column.
The table school_info_l has many contraints that affect other tables however
> Also, is it always the same number in the error, or does that change
> from run to run?
The number is the same for each time I run the update file on the same
database. with this two queries having the same error.
Same result to, if I run these two after the first update file
finishes there is no problem, but if I try to run it at the end of hte
first file, choke.
Very Odd problem to me, since the update statemenets are so simple.
-Tom
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2004-08-13 17:19:15 | Re: [PERFORM] Performance Problem With Postgresql! |
Previous Message | Pentilian | 2004-08-13 16:05:39 | Re: Wierd Error on update |