Shalendra Tripathi wrote: > > Hi, > > I am facing some problem during upgrade from slony-1 1.1.5 to 1.2.9. I > am having a cluster setup with 2 nodes. Slony got upgraded > successfully from new rpm but I got following error when I was trying > to run the slonik <http://slony.info/documentation/slonik.html> > command UPDATE FUNCTIONS > <http://slony.info/documentation/stmtupdatefunctions.html>on both nodes. > > ************************************************************************************************************* > > <stdin>:6: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit > index "sl_registry_pkey" for table "sl_registry" > CONTEXT: SQL statement "create table "_mswcluster".sl_registry ( > reg_key text primary key, > reg_int4 int4, > reg_text text, > reg_timestamp timestamp > ) without oids" > PL/pgSQL function "upgradeschema" line 75 at execute statement > <stdin>:6: commit transaction; - server closed the connection unexpectedly > This probably means the server terminate > > ************************************************************************************************ > > Although replication is going on smoothly but I wanted to know the > exact reason of this error. Could this can cause any problem further. > > Thanks > Shalendra Tripathi Question: What version of PostgreSQL are you on?
If you're on 8.1.0 thru 8.1.3, then there is a known problem that causes Slony-I upgrades to break :-(. http://linuxfinances.info/info/faq.html#AEN46382 *Q: I'm trying to upgrade to a newer version of Slony-I and am running into a problem with UPDATE FUNCTIONS(7) <http://linuxfinances.info/info/stmtupdatefunctions.html>. When I run UPDATE FUNCTIONS(7) <http://linuxfinances.info/info/stmtupdatefunctions.html>, my *postmaster* falls over with a Signal 11. There aren't any seeming errors in the log files, aside from the PostgreSQL logs indicating that, yes indeed, the postmaster fell over.* I connected a debugger to the core file, and it indicates that it was trying to commit a transaction at the time of the failure. By the way I'm on PostgreSQL 8.1.[0-3]. *A: * Unfortunately, early releases of PostgreSQL 8.1 had a problem where if you redefined a function (such as, say, |upgradeSchema(text)|), and then, in the same transaction, ran that function, the *postmaster* would fall over, and the transaction would fail to commit. The *slonik*(1) <http://linuxfinances.info/info/slonik.html> command UPDATE FUNCTIONS(7) <http://linuxfinances.info/info/stmtupdatefunctions.html> functions like that; it, in one transaction, tries to: * Load the new functions (from slony1_funcs.sql), notably including |upgradeSchema(text)|. * Run |upgradeSchema(text)| to do any necessary upgrades to the database schema. * Notify *slon*(1) <http://linuxfinances.info/info/slon.html> processes of a change of configuration. Unfortunately, on PostgreSQL 8.1.0, 8.1.1, 8.1.2, and 8.1.3, this conflicts with a bug where using and modifying a plpgsql function in the same transaction leads to a crash. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
