Thread: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
From
PG Bug reporting form
Date:
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 Please let me know if any further information required.
Re: BUG #16473: Marked as broken because ofSQLSTATE(08006),ErrorCode(0)
From
Kyotaro Horiguchi
Date:
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
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
Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
From
Brajendra Pratap Singh
Date:
Hi,
Thanks,
Thanks for ur response.
Could you plz let me know ,what cause this error "Marked as broken because of SQLSTATE(08006),ErrorCode(0)" .
Brajendra
On Wed, 3 Jun, 2020, 3:39 AM Dave Cramer, <davecramer@postgres.rocks> wrote:
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 anythingDave Cramerwww.postgres.rocks
On Tue, 2 Jun 2020 at 19:31, Brajendra Pratap Singh <singh.bpratap766@gmail.com> wrote:
Hi,Thanks for ur response.Could you plz let me know ,what cause this error "Marked as broken because of SQLSTATE(08006),ErrorCode(0)" .
The message is telling you that you ran out of memory fetching the data. I presume the table is very big and the select is not very selective.
Dave Cramer
www.postgres.rocks