| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Blake McBride <blake1024(at)gmail(dot)com> |
| Cc: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org |
| Subject: | Re: JDBC: ERROR: portal "C_2" does not exist |
| Date: | 2022-03-11 20:20:35 |
| Message-ID: | CAB=Je-FT2PxtXUYD+ricnfFrOHMtfbXOpjm_8aspd2PQRzBwyA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>Just knowing it should work is a big help.
That is true.
The error <<portal "C_2" does not exist>> should not happen in the regular
app flow.
The symptom reminds me "do not close refcursor after reading if fetchsize
has been set"
https://github.com/pgjdbc/pgjdbc/pull/2371 (v42.3.2+),
so I wonder if the issue reproduces with v42.3.1
We can't heal wong load-balancer configurations at the driver level,
however, we could make the error message easier to understand and diagnose.
I've filed https://github.com/pgjdbc/pgjdbc/issues/2468 for enhancing the
user-facing message.
Yet another option to diagnose the issue is to capture trace logs from the
driver.
See https://jdbc.postgresql.org/documentation/head/logging.html
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Blake McBride | 2022-03-12 03:45:23 | Re: JDBC: ERROR: portal "C_2" does not exist |
| Previous Message | Blake McBride | 2022-03-11 19:56:02 | Re: JDBC: ERROR: portal "C_2" does not exist |