|
Home > Archive > Slony1 PostgreSQL Replication > July 2005 > ERROR: cache lookup failed for relation 438095645
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ERROR: cache lookup failed for relation 438095645
|
|
| Joe Markwardt 2005-07-07, 11:24 am |
| Greetings all,
I'm posting this question here per suggestion from Tom Lane on the
postgres-general mailing list.
The thread on the postgres list:
http://archives.postgresql.org/pgsq...07/msg00126.php
Basically what lead up to this was I needed to drastically change the
structure of the pl_inventory_analyze
r_files_table so I dropped the
table from replication, dropped and recreated it on the provider with no
problems, went to drop and recreate it on the subscriber and got the
error in the subject.
So I guess what I'm looking for is how to fix this error so I can drop
the table, recreate it and get on with life. Hopefully without dropping
the entire subscriber node and re-subscribing. Course if I have to do
that I may as well make the jump from 1.05 to 1.1 at the same time :)
Thanks for your time,
Joe
| |
| Jan Wieck 2005-07-07, 11:24 am |
| On 7/7/2005 11:54 AM, Joe Markwardt wrote:
> Greetings all,
> I'm posting this question here per suggestion from Tom Lane on the
> postgres-general mailing list.
>
> The thread on the postgres list:
> http://archives.postgresql.org/pgsq...07/msg00126.php
>
> Basically what lead up to this was I needed to drastically change the
> structure of the pl_inventory_analyze
r_files_table so I dropped the
> table from replication, dropped and recreated it on the provider with no
> problems, went to drop and recreate it on the subscriber and got the
> error in the subject.
>
> So I guess what I'm looking for is how to fix this error so I can drop
> the table, recreate it and get on with life. Hopefully without dropping
> the entire subscriber node and re-subscribing. Course if I have to do
> that I may as well make the jump from 1.05 to 1.1 at the same time :)
Did you just throw the DDL via psql at the databases or did you do it
with the appropriate slonik command?
http://gborg.postgresql.org/project... />
_ddl_script
In case you didn't know about execute script, you probably are best off
to use "uninstall node" for all nodes and reinstall slony from scratch.
Jan
>
> Thanks for your time,
> Joe
>
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
--
#===================
====================
====================
===========#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#===================
====================
=========== JanWieck- bwPqjjyvM7QAvxtiuMwx
3w@public.gmane.org #
|
|
|
|
|