On 4/4/2006 2:49 PM, Glen Eustace wrote:

> Table 9 still exists in _gz_admin.sl_table;
> 
>       9 |    9527801 | domain_registry_history | public      |       3 |
> domain_registry_history_pkey | t           | Domain Registry
> 
> and still exists for real in the database.

This is odd. Can it be that the table has been dropped and recreated, 
and thereby it's OID changed? If the tables OID in pg_class is different 
from the tab_reloid in sl_table (9527801), that would explain the error.

There is an (undocumented?) slonik command

   REPAIR CONFIG
     (set id = <int>[, event node = <int>] [, execute only on = <int>]);

Which should take care of this problem.

Why is it undocumented? Chris?


Jan

> 
> It has the following rules and indices;
> Indexes:
>     "domain_registry_history_pkey" PRIMARY KEY, btree ("domain", tstamp)
>     "domain_registry_history_idx1" btree (client, "domain", tstamp)
> Triggers:
>     _gz_admin_logtrigger_9 AFTER INSERT OR DELETE OR UPDATE ON
> domain_registry_history FOR EACH ROW EXECUTE PROCEDURE
> _gz_admin.logtrigger('_gz_admin', '9', 'vkkvvvvvvvvvvvvv')
> 
> It also has a view which includes update rules.
> 
> Where to next ?
> 


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #