Re: BUG #16473: Marked as broken because ofSQLSTATE(08006),ErrorCode(0) - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: BUG #16473: Marked as broken because ofSQLSTATE(08006),ErrorCode(0)
Date
Msg-id 20200602.152056.1498116775596920293.horikyota.ntt@gmail.com
Whole thread Raw
In response to BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-bugs
Hello.

At Mon, 01 Jun 2020 13:52:06 +0000, PG Bug reporting form <noreply@postgresql.org> wrote in 
> The following bug has been logged on the website:
> 
> Bug reference:      16473
> Logged by:          Brajendra Pratap Singh
> Email address:      singh.bpratap766@gmail.com
> PostgreSQL version: 10.8
> Operating system:   CentOS 6.9
> Description:        
> 
> We are getting the below error in postgresql db application log .
> 
> 1) Marked as broken because of SQLSTATE(08006),ErrorCode(0) 
> 
> And after that we get below error 
> Ran out of memory retrieving query result

This doesn't seem to be a bug of PostgreSQL.

> Please let me know if any further information required.

The messages don't seem to be of PostgreSQL but some googling told me
that it comes from JDBC driver.  The underlying Java VM doesn't offer
enough amount of heap memory for the result.  Maybe you can use
setFetchSize() to limit the number of result sent from the server at
once.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgbench bug / limitation
Next
From: Konstantin Knizhnik
Date:
Subject: Problem with accessing OTAST data in stored procedures