Thanks for your reply. I think I get rid of double entry. What I did is to make the ports different for load balancer and cluster db1. Like 5432 for cluster db1 and 5433 for load balancer. Does it make different result ? What do you think ?
Thanks On 5/28/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > In order to make clear your environment, please let me know as follows, > > 1. Which server do you send the insert query, load balancer or cluster2? > 2. Contents of the insert query. > 3. Debug log of replication server and load balancer > 4. The setting of all configuration files in each servers. > > Regards, > ---------------- > At.Mitani > > -- original message -- > From: Chahyeon Rhee<[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wed, 28 May 2008 09:46:21 -0600 > Subject: [Pgcluster-general] Double Insert > > >Hi! Everyone, > >I tried to set up pgcluster and I have some problem. > >I have two server: server1 and server2. > >Server1 has load balance and cluster db1. > >Server2 has cluster db2 and replicator. > >And I am using postgres 8.1.11 and pgCluster 1.5.0.rc21 > >The problem is that when I test the case that the server 1 is down, > somtimes > >I can insert correctly one time into server2 but sometimes insert is done > >twice. > >Each case has different stop processing message. > >In the below, the first is the case for correct case. And second is for > >double inserts. > >Please give me any advice. > > > >Thanks in advance. > > > >-bash-3.00$ pg_ctl stop -D /var/lib/pgsql/data > >LOG: received smart shutdown request > >waiting for postmaster to shut down....lifecheck stopped > >............FATAL: the database system is shutting down > >LOG: server process (PID 14659) was terminated by signal 11 > >LOG: terminating any other active server processes > >FATAL: the database system is shutting down > >WARNING: terminating connection because of crash of another server > process > >DETAIL: The postmaster has commanded this server process to roll back the > >current transaction and exit, because another server process exited > >abnormally and possibly corrupted shared memory. > >HINT: In a moment you should be able to reconnect to the database and > >repeat your command. > >LOG: all server processes terminated; reinitializing > >LOG: database system was interrupted at 2008-05-28 09:22:11 MDT > >LOG: checkpoint record is at 0/4AC684 > >LOG: redo record is at 0/4AC684; undo record is at 0/0; shutdown TRUE > >LOG: next transaction ID: 67814; next OID: 16394 > >LOG: next MultiXactId: 1; next MultiXactOffset: 0 > >LOG: database system was not properly shut down; automatic recovery in > >progress > >FATAL: the database system is shutting down > >FATAL: the database system is shutting down > >FATAL: the database system is shutting down > >FATAL: the database system is shutting down > >LOG: redo starts at 0/4AC6C8 > >LOG: record with zero length at 0/4ADC2C > >LOG: redo done at 0/4ADC04 > >LOG: database system is ready > >LOG: transaction ID wrap limit is 1073809584, limited by database > >"template1" > >LOG: shutting down > >LOG: database system is shut down > > done > >postmaster stopped > > > > > > > >-bash-3.00$ pg_ctl stop -D /var/lib/pgsql/data > >LOG: received smart shutdown request > >lifecheck stopped > >waiting for postmaster to shut down...LOG: shutting down > >.LOG: database system is shut down > > done > >postmaster stopped > > > >_______________________________________________ > >Pgcluster-general mailing list > >[email protected] > >http://pgfoundry.org/mailman/listinfo/pgcluster-general > > > > _______________________________________________ > Pgcluster-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgcluster-general >
_______________________________________________ Pgcluster-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgcluster-general
