Bristol Digest, Vol 594, Issue 2

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Postgres problem (Martin Moore)


----------------------------------------------------------------------

Message: 1
Date: Thu, 19 Mar 2015 15:20:30 -0000
From: "Martin Moore" <martinm@it-helps.co.uk>
To: "'Bristol and Bath Linux User Group'" <bristol@mailman.lug.org.uk>
Subject: [bristol] Postgres problem
Message-ID:
<!&!AAAAAAAAAAAYAAAAAAAAAFLxZtQqo65Oo+1jhlUB9DvCgAAAEAAAAGFJCD297OtOv/tthHx4mp8BAAAAAA==@it-helps.co.uk>

Content-Type: text/plain; charset="us-ascii"

I've just moved serverA to a new datacentre. Before the move it was
replicating via slony to server quite happily (at least I think so..).

Both are running Jessie, postgres 9.3 and slony 2.2.2-1 (did a system
upgrade 2 days ago so all should be the latest)


I can't get the slony scripts to complete, and have got to the point where I
may have found an indication to the problem.

On serverA (T1 stuff is after slony has been installed)

>\d country;
Table "public.country"
Column | Type | Modifiers
------------+--------------+------------------------------------------------
--------------
country_id | integer | not null default
nextval(('country_id_seq'::text)::regclass)
prefix | character(2) | not null
state | text |
region | character(3) |
listorder | smallint |
Indexes:
"country_pkey" PRIMARY KEY, btree (country_id)
"country_prefix" btree (prefix)
Triggers:
"_T1_logtrigger" AFTER INSERT OR DELETE OR UPDATE ON country FOR EACH
ROW EXECUTE PROCEDURE "_T1".logtrigger('_T1', '2004', 'k')
"_T1_truncatetrigger" BEFORE TRUNCATE ON country FOR EACH STATEMENT
EXECUTE PROCEDURE "_T1".log_truncate('2004')
Disabled triggers:
"_T1_denyaccess" BEFORE INSERT OR DELETE OR UPDATE ON country FOR EACH
ROW EXECUTE PROCEDURE "_T1".denyaccess('_T1')
"_T1_truncatedeny" BEFORE TRUNCATE ON country FOR EACH STATEMENT EXECUTE
PROCEDURE "_T1".deny_truncate()


serverB
> \d country
ERROR: cache lookup failed for function 666504


I get the same for some other tables.
Hopefully if I can fix this the slony stuff will start working (it's
complaining the trigger already exists for this table)


Anyone got any thoughts? Even how to find out what function 666504 is!



Cheers,

Martin.




------------------------------

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 594, Issue 2
***************************************