Michael Cheung vividy at justware.co.jp
Tue Nov 22 05:00:34 PST 2011
Hi all;
(postgres version 8.3.16, slony version 2.1.0)

While I run sql to create index on a huge table(named tableA) by slonik_execute_script,
(actually this operation cost me almost 20 min.)
And slonik_execute_script command end with following error message.

<stdin>:5: NOTICE:  public.tableB has an invalid configuration on the log trigger. This was not corrected because
only_lock is true and the table is not locked.
CONTEXT:  SQL statement "SELECT  "_apl_repl1".repair_log_triggers(true)"
PL/pgSQL function "ddlscript_complete_int" line 5 at PERFORM
SQL statement "SELECT  "_apl_repl1".ddlScript_complete_int( $1 , $2 )"
PL/pgSQL function "ddlscript_complete" line 7 at PERFORM

And I have check the new index on table A on every node, it is created and seems fine.
And record count on tableB is same on every node. Everything seems well.

But anyone can tell me what happened with this message? And is it safe to just ignore it?

Thanks a lot.

Michael



More information about the Slony1-general mailing list