[Pgpool-general] Pgpool-II - replication problems

[Tatsuo Ishii]

Thanks. I think I have figured out what's going on. pgpool tries to
start a new transaction if DML (for example INSERT) is sent. The
particular setting you use with PostgreSQL generates lots of DEBUG and
NOTICE messages while processing BEGIN and they make pgpool
confused. I have committed a fix for this. The new tar ball was put on
the same location as before. Can you please grab and try it again?
--
Tatsuo Ishii
SRA OSS, Inc. Japan

> Postgresql.conf it attached
> 
> Thank You!
> 
> Nir
> 
> On Wed, Nov 12, 2008 at 12:51 AM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:
> 
> > Thanks for the feedback. Could you show me postgresql.conf?
> > --
> > Tatsuo Ishii
> > SRA OSS, Inc. Japan
> >
> > > Hi Tatsuo,
> > >
> > > THANK YOU!
> > > I was able to download the file, and install it (configure, make & make
> > > install).
> > >
> > > I run the command again and here are the log file you asked for:
> > >
> > >  psql -p 9999 -c "INSERT INTO branches  VALUES (3,1,' ')"
> > > ============================================
> > > DEBUG:  InitPostgres
> > > DEBUG:  StartTransaction
> > > DEBUG:  name: unnamed; blockState:       DEFAULT; state: INPROGR,
> > > xid/subid/cid: 28279195/1/0, nestlvl: 1, children: <>
> > > DEBUG:  CommitTransaction
> > > DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR,
> > > xid/subid/cid: 28279195/1/0, nestlvl: 1, children: <>
> > > server closed the connection unexpectedly
> > >         This probably means the server terminated abnormally
> > >         before or while processing the request.
> > > connection to server was lost
> > >
> >