BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: nehemadhuri(at)gmail(dot)com
Subject: BUG #18534: ERROR: portal "C_n" does not exist type of error getting thrown.
Date: 2024-07-12 09:31:48
Message-ID: 18534-911bd7dcafa8afca@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18534
Logged by: madhuri nehe
Email address: nehemadhuri(at)gmail(dot)com
PostgreSQL version: 15.3
Operating system: Linux
Description:

1. This issue occurs in multithreaded application.
2. We retrieve records from a single table and store them in the ResultSet
object of JDBC.
3. To read the records sequentially from the ResultSet object, we employ the
rSet.next() method for iteration.
4. We are encountering a sporadic portal exception triggered by the
rSet.next() method call.
5. We have examined all potential causes, such as verifying the executed
query, checking if the ResultSet cursor is open or closed, ensuring the
database connection object is active, and confirming the prepared statement
cursor’s status. No issues have been detected. Also, ResultSet is not being
accessed by multiple threads simultaneously.

We've been thorough in our search for the cause of the issue but haven't
found anything yet.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2024-07-12 10:57:05 Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert
Previous Message Alexander Kukushkin 2024-07-12 09:00:24 Re: pg_rewind WAL segments deletion pitfall