Thu Mar 13 06:59:21 PDT 2008
- Previous message: [Slony1-general] Slave upgrade without break replication
- Next message: [Slony1-general] Replication problem of "BIG" table - COPY event in a loop
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all,
we have problem to replicate 12 GB table.
Note: Other smaller tables were replicated without problem.
Here is what I see on "slave" node.
$ grep 'action"' /var/log/slony1/slon-db.log
DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."action"
DEBUG2 remoteWorkerThread_1: copy table "public"."action"
DEBUG2 remoteWorkerThread_1: Begin COPY of table "public"."action"
NOTICE: truncate of "public"."action" failed - doing delete
DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."action"
DEBUG2 remoteWorkerThread_1: copy table "public"."action"
DEBUG2 remoteWorkerThread_1: Begin COPY of table "public"."action"
NOTICE: truncate of "public"."action" failed - doing delete
DEBUG2 remoteWorkerThread_1: 6584477358 bytes copied for table
"public"."action"
DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."action"
DEBUG2 remoteWorkerThread_1: copy table "public"."action"
DEBUG2 remoteWorkerThread_1: Begin COPY of table "public"."action"
NOTICE: truncate of "public"."action" failed - doing delete
DEBUG2 remoteWorkerThread_1: 6587572735 bytes copied for table
"public"."action"
DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."action"
DEBUG2 remoteWorkerThread_1: copy table "public"."action"
DEBUG2 remoteWorkerThread_1: Begin COPY of table "public"."action"
NOTICE: truncate of "public"."action" failed - doing delete
I can't find any error message in the log.
COPY event for this "big" table is in a loop and table size on "slave"
node is still growing.
On "Master" node, the table size is 12GB.
On "Slave" node the tables size was 68GB before I have stopped the
replication.
-------------
OS: Ubuntu 6.06.2 LTS , 2.6.15-29-amd64-server, x86_64
DB: postgresql-8.1
SLONY: Version: 1.2.9-2ubuntu0~dapper0
Detail of our problematic "12GB" table
=# \d+ action;
Table "public.action"
Column | Type |
Modifiers | Description
------------+-----------------------------+-----------------------------------------------------+-------------
id | integer | not null default
nextval('action_id_seq'::regclass) |
clientid | integer |
|
action | integer | not null
|
response | integer |
|
startdate | timestamp without time zone | not null default now()
|
clienttrid | character varying(128) | not null
|
enddate | timestamp without time zone |
|
servertrid | character varying(128) |
|
Indexes:
"action_pkey" PRIMARY KEY, btree (id)
"action_servertrid_key" UNIQUE, btree (servertrid)
"action_action_idx" btree ("action")
"action_clientid_idx" btree (clientid)
"action_response_idx" btree (response)
"action_startdate_idx" btree (startdate)
Foreign-key constraints:
"action_action_fkey" FOREIGN KEY ("action") REFERENCES enum_action(id)
"action_clientid_fkey" FOREIGN KEY (clientid) REFERENCES "login"(id)
"action_response_fkey" FOREIGN KEY (response) REFERENCES enum_error(id)
---------------
Does anyone have an idea what could be wrong?
Thanks,
Petr
- Previous message: [Slony1-general] Slave upgrade without break replication
- Next message: [Slony1-general] Replication problem of "BIG" table - COPY event in a loop
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list