From: | Dave Youatt <dave(at)meteorsolutions(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Slony-I: cache lookup failed for type 267501 |
Date: | 2009-06-11 22:05:06 |
Message-ID: | 4A317F92.90109@meteorsolutions.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Help?
Just configured a Slony-I cluster, two nodes, Centos 5.2 x64, master
logging errors like the excerpt below almost continuously. stopped the
slon daemons, and dropped replication on each node for now.
There were two file sets, one of 7 tables, and another of 21 tables. I
believe it was in the process of copying one of the large tables in the
first set to the slave.
2009-06-11 15:44:10.752 CDTERROR: cache lookup failed for type 267501
2009-06-11 15:44:10.752 CDTCONTEXT: SQL statement "INSERT INTO
_meteorstats.sl_log_1 (log_origin, log_xid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata) VALUES (1, $1, $2,
nextval('_meteorstats.sl_action_seq'), $3, $4);"
SQL function "increment_url_visits" statement 1
2009-06-11 15:44:10.752 CDTSTATEMENT: select increment_url_visits($1,$2)
2009-06-11 15:44:10.756 CDTERROR: cache lookup failed for type 267501
2009-06-11 15:44:10.756 CDTCONTEXT: SQL statement "INSERT INTO
_meteorstats.sl_log_1 (log_origin, log_xid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata) VALUES (1, $1, $2,
nextval('_meteorstats.sl_action_seq'), $3, $4);"
SQL function "increment_url_visits" statement 1
2009-06-11 15:44:10.756 CDTSTATEMENT: select increment_url_visits($1,$2)
2009-06-11 15:44:10.765 CDTERROR: cache lookup failed for type 267501
2009-06-11 15:44:10.765 CDTCONTEXT: SQL statement "INSERT INTO
_meteorstats.sl_log_1 (log_origin, log_xid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata) VALUES (1, $1, $2,
nextval('_meteorstats.sl_action_seq'), $3, $4);"
SQL function "increment_url_visits" statement 1
Master rpms:
compat-postgresql-libs-4-1PGDG.rhel5
postgresql-server-8.3.6-1PGDG.rhel5
postgresql-libs-8.1.11-1.el5_1.1
postgresql-libs-8.3.6-1PGDG.rhel5
postgresql-8.3.6-1PGDG.rhel5
postgresql-devel-8.3.6-1PGDG.rhel5
postgresql-contrib-8.3.6-1PGDG.rhel5
postgresql-docs-8.3.6-1PGDG.rhel5
slony1-docs-1.2.15-3.rhel5
slony1-1.2.15-3.rhel5
Slave rpms:
postgresql-8.3.7-1PGDG.rhel5
postgresql-contrib-8.3.7-1PGDG.rhel5
postgresql-libs-8.1.11-1.el5_1.1
postgresql-server-8.3.6-1PGDG.rhel5
postgresql-docs-8.3.6-1PGDG.rhel5
postgresql-libs-8.3.7-1PGDG.rhel5
postgresql-server-8.3.7-1PGDG.rhel5
postgresql-plpython-8.3.7-1PGDG.rhel5
postgresql-devel-8.3.7-1PGDG.rhel5
compat-postgresql-libs-4-1PGDG.rhel5
postgresql-python-8.1.11-1.el5_1.1
slony1-docs-1.2.15-3.rhel5
slony1-1.2.15-3.rhel5
Noticed that there are updated slony1 rpms, but don't want to start
playing rpm roulette, just yet.
Same two servers had been replicating happily for months, but only 5 tables.
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Shellam | 2009-06-11 22:26:17 | Re: pg_dump not appending sequence to default values |
Previous Message | Emanuel Calvo Franco | 2009-06-11 21:41:56 | Re: Replication with SQL Server 2k |