Wed Jan 30 02:51:19 PST 2008
- Previous message: [Slony1-general] Slony-I not setting up replication triggers (though defined)
- Next message: [Slony1-general] list active nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I have checked out slony-1 source code from cvs and tried compiling with PostgreSQL 8.3 RC2(checkout version). I was able to compile it but slony tests are failing. Has anyone faced this problem? Is there some issue with Slony code? Please let me know if I need to attach any logs. All the slony tests are failing but I am attaching the logs for only one test(testmergeset). SLONY TEST LOG: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D bash-3.2$ PGBINDIR=3D/space/WORK/postgres/bin/ PGUSER=3Dsatya ./run_test.sh testmergeset test: testmergeset ---------------------------------------------------- $Id: README,v 1.2 2007-10-26 14:47:24 cbbrowne Exp $ testmergeset sets up a series of replication sets, progressively merging them together. This was written based on "testpartition", the difference being that in this test, tables are added to replication via explicitly creating a set (a temporary set #999), and then merging that set back into the main set. This test also takes a fairly aggressive tack on usage of WAIT FOR EVENT; when it gets into the "merge phase," it submits a SYNC followed by waiting for that SYNC to be confirmed on all relevant nodes before submitting a MERGE SET request to eliminate the extra set. It does not use any SLEEP requests; concurrency control is expected to be controlled by WAIT FOR EVENT. ---------------------------------------------------- Test by j.random.luser at example.net to be summarized in /tmp/Slony- I-test-results.log creating origin DB: satya -h localhost -U satya -p 5432 slonyregress1 add plpgsql to Origin loading origin DB with testmergeset/init_schema.sql setting up user satya to have weak access to data done creating subscriber 2 DB: satya -h localhost -U satya -p 5432 slonyregress2 add plpgsql to subscriber loading subscriber 2 DB from slonyregress1 done creating subscriber 3 DB: satya -h localhost -U satya -p 5432 slonyregress3 add plpgsql to subscriber loading subscriber 3 DB from slonyregress1 done creating subscriber 4 DB: satya -h localhost -U satya -p 5432 slonyregress4 add plpgsql to subscriber loading subscriber 4 DB from slonyregress1 done creating cluster done storing nodes done Granting weak access on Slony-I schema done storing paths done launching originnode : /space/WORK/postgres/bin//slon -s500 -g10 -d2 slony_regress1 "dbname=3Dslonyregress1 host=3Dlocalhost user=3Dsatya port= =3D5432" Archive node: Considering node 2 launching: /space/WORK/postgres/bin//slon -s500 -g10 -d2 slony_regress1 "dbname=3Dslonyregress2 host=3Dlocalhost user=3Dsatya port=3D5432" Considering node 3 launching: /space/WORK/postgres/bin//slon -s500 -g10 -d2 slony_regress1 "dbname=3Dslonyregress3 host=3Dlocalhost user=3Dsatya port=3D5432" Considering node 4 launching: /space/WORK/postgres/bin//slon -s500 -g10 -d2 slony_regress1 "dbname=3Dslonyregress4 host=3Dlocalhost user=3Dsatya port=3D5432" subscribing and HANGS at this stage.. Postgres Log =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D LOG: database system was shut down at 2008-01-30 16:12:30 IST LOG: autovacuum launcher started LOG: database system is ready to accept connections NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "regions_pkey" for table "regions" NOTICE: CREATE TABLE will create implicit sequence "products_product_id_seq" for serial column "products.product_id" NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "products_pkey" for table "products" NOTICE: CREATE TABLE / UNIQUE will create implicit index "products_name_key" for table "products" NOTICE: CREATE TABLE will create implicit sequence "sales_txns_id_seq" for serial column "sales_txns.id" NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "sales_txns_pkey" for table "sales_txns" ERROR: relation "public.table1" does not exist STATEMENT: grant select on table public.table1 to satya; ERROR: relation "public.table1_id_seq" does not exist STATEMENT: grant select on table public.table1_id_seq to satya; ERROR: relation "public.table2" does not exist STATEMENT: grant select on table public.table2 to satya; ERROR: relation "public.table2_id_seq" does not exist STATEMENT: grant select on table public.table2_id_seq to satya; ERROR: relation "public.table1a" does not exist STATEMENT: grant select on table public.table1a to satya; ERROR: relation "public.table1a_id_seq" does not exist STATEMENT: grant select on table public.table1a_id_seq to satya; ERROR: relation "public.table2a" does not exist STATEMENT: grant select on table public.table2a to satya; ERROR: relation "public.table2a_id_seq" does not exist STATEMENT: grant select on table public.table2a_id_seq to satya; ERROR: Missing sales_txns partition for date 2006-01-15 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-15') from regions, products order by random() limit 3; ERROR: Missing sales_txns partition for date 2006-01-16 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-16') from regions, products order by random() limit 3; ERROR: Missing sales_txns partition for date 2006-01-17 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-17') from regions, products order by random() limit 3; ERROR: Missing sales_txns partition for date 2006-01-18 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-18') from regions, products order by random() limit 3; ERROR: Missing sales_txns partition for date 2006-01-19 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-19') from regions, products order by random() limit 3; ERROR: Missing sales_txns partition for date 2006-01-20 00:00:00+05:30 CONTEXT: SQL statement "INSERT INTO sales_txns (region_code, product_id, quantity, amount, trans_on) values ( $1 , $2 , $3 , $4 , $5 )" PL/pgSQL function "purchase_product" line 11 at SQL statement STATEMENT: select purchase_product( region_code, product_id, (random()*5+random()*8+random()*7)::integer, '2006-01-20') from regions, products order by random() limit 3; ERROR: language "plpgsql" already exists STATEMENT: CREATE PROCEDURAL LANGUAGE plpgsql; NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index "products_name_key" for table "products" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "products_pkey" for table "products" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "regions_pkey" for table "regions" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "sales_txns_pkey" for table "sales_txns" ERROR: language "plpgsql" already exists STATEMENT: CREATE PROCEDURAL LANGUAGE plpgsql; NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index "products_name_key" for table "products" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "products_pkey" for table "products" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "regions_pkey" for table "regions" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "sales_txns_pkey" for table "sales_txns" ERROR: language "plpgsql" already exists Regards, Satya -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080130/= 727c3804/attachment.htm
- Previous message: [Slony1-general] Slony-I not setting up replication triggers (though defined)
- Next message: [Slony1-general] list active nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list