From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Portal suddenly disappears? |
Date: | 2014-01-15 06:11:06 |
Message-ID: | 20140115.151106.2214171434332266443.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> The portal "portal19528" was created by a bind message (pgpool-II uses
>> the identical name as the named statement) then subsequent
>> exec_bind_message failed to find the portal. Could it ever happen?
>
> I'm confused too. Surely there are lots of ways a portal could get
> dropped, but most of them would have left traces in the postmaster log,
> I'd think, since you evidently have log_statement == LOGSTMT_ALL.
> What was log_min_messages set to?
I don't have it at this moment. I requested the user to give the
log_min_messages setting.
>> According to the user, PostgreSQL version is 8.1.23. Could it be a
>> source of problem?
>
> However, it's pretty hard to get excited about debugging something
> that happened in a release branch that's been out of support for
> more than three years.
Right. I will ask the user to upgrade to supported versions.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-01-15 06:23:25 | Re: plpgsql.consistent_into |
Previous Message | Florian Pflug | 2014-01-15 06:07:12 | Re: plpgsql.warn_shadow |