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

From Dave Cramer
Subject Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
Date
Msg-id CADK3HHK-Svz2rsLcJv=p4=3KXD+dx+6uSXyQG4OTAZ9UyfzT=w@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16473: Marked as broken because ofSQLSTATE(08006),ErrorCode(0)  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)  (Brajendra Pratap Singh <singh.bpratap766@gmail.com>)
List pgsql-bugs


On Tue, 2 Jun 2020 at 02:21, Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
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.


If so you need to make sure you are in a transaction, otherwise setFetchSize does not do anything


Dave Cramer
www.postgres.rocks

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: FailedAssertion("!OidIsValid(def->collOid)", File: "view.c",Line: 89)
Next
From: PG Bug reporting form
Date:
Subject: BUG #16475: mess up my laptop