[pgpool-general: 1026] Re: Pgpool thread crash, 1 DB backend, replication mode on - Minor

Tatsuo Ishii ishii at postgresql.org
Thu Sep 20 07:49:16 JST 2012


Not reproduced here. Can you show backtrace?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> It really would have been helpful to include the version...           : )
> 
> We're testing version 3.2.0, built from source, running on Cent OS 6.3-x86_64, with the backend node running PostgreSQL 9.2.0.
> 
> 
>         - Matt
> 
> 
> 
> -----------------------------------
> Matthew Sell
> Software Engineer III
> New Products Introduction Group
> Fluke Corporation
> 
> 
>> -----Original Message-----
>> From: Tatsuo Ishii [mailto:ishii at postgresql.org]
>> Sent: Wednesday, September 19, 2012 3:28 PM
>> To: Sell, Matt
>> Cc: pgpool-general at pgpool.net
>> Subject: Re: [pgpool-general: 1022] Pgpool thread crash, 1 DB backend,
>> replication mode on - Minor
>> 
>> > We've observed a case where if "replication_mode" is "on", and there is
>> only one backend defined, that occasionally when a client connects and
>> executes a query the pgpool worker thread segfaults.
>> >
>> > This isn't a production instance of pgpool that this happened on, it was a
>> test instance where I accidently left replication enabled and removed all
>> backends except for one.
>> >
>> > The simple obvious workaround was to disable replication mode, since
>> there wasn't anything else for pgpool to replicate to anyway.
>> >
>> >
>> > Just a heads-up in case anyone else experiences pgpool segfaults under
>> similar conditions.
>> 
>> What version of pgpool are you using?
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese: http://www.sraoss.co.jp
> 
> 


More information about the pgpool-general mailing list