[pgpool-general: 6232] Re: PGPOOL Error with DEALLOCATE

[Bo Peng]

Hi,

Thank you for reporting this bug.
I will look into it.

On Wed, 5 Sep 2018 17:14:10 +0000
"Kumar, Virendra" <Virendra.Kumar at guycarp.com> wrote:

> Hi PGPOOL Developers,
> 
> When we run a simple deallocate command using pgpool as loadbalancer in master-slave mode while the connection is on standby server we are getting below error. I read it somewhere that it is fixed but surprisingly this is not the case. We are using pgpool 3.7.1:
> --
> ap_sit_db=# PREPARE usrrptplan (int) AS select count(*) from ap.site_exposure_p1;
> PREPARE
> ap_sit_db=# select * from pg_prepared_statements;
>     name    |                               statement                               |         prepare_time          | parameter_types | from_sql
> ------------+-----------------------------------------------------------------------+-------------------------------+-----------------+----------
> usrrptplan | PREPARE usrrptplan (int) AS select count(*) from ap.site_exposure_p1; | 2018-09-04 12:12:28.449465-05 | {integer}       | t
> (1 row)
> 
> 
> ap_sit_db=#
> ap_sit_db=# EXECUTE usrrptplan(2);
> count
> --------
> 171721
> (1 row)
> 
> ap_sit_db=# DEALLOCATE usrrptplan;
> WARNING:  packet kind of backend 1 ['E'] does not match with master/majority nodes packet kind ['C']
> FATAL:  failed to read kind from backend
> DETAIL:  kind mismatch among backends. Possible last query was: "DEALLOCATE usrrptplan;" kind details are: 0[C] 1[E: prepared statement "usrrptplan" does not ex
> ist]
> HINT:  check data consistency among db nodes
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Succeeded.
> 
> 
> Regards,
> Virendra
> 
> 
> ________________________________
> 
> This message is intended only for the use of the addressee and may contain
> information that is PRIVILEGED AND CONFIDENTIAL.
> 
> If you are not the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please erase all copies of the message
> and its attachments and notify the sender immediately. Thank you.


-- 
Bo Peng <pengbo at sraoss.co.jp>
SRA OSS, Inc. Japan