pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
5+ messages / 4 participants
[nested] [flat]
* BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
@ 2020-06-01 13:52 PG Bug reporting form <noreply@postgresql.org>
2020-06-02 06:20 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Kyotaro Horiguchi <horikyota.ntt@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: PG Bug reporting form @ 2020-06-01 13:52 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: singh.bpratap766@gmail.com
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.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
2020-06-01 13:52 BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) PG Bug reporting form <noreply@postgresql.org>
@ 2020-06-02 06:20 ` Kyotaro Horiguchi <horikyota.ntt@gmail.com>
2020-06-02 22:09 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Dave Cramer <davecramer@postgres.rocks>
0 siblings, 1 reply; 5+ messages in thread
From: Kyotaro Horiguchi @ 2020-06-02 06:20 UTC (permalink / raw)
To: singh.bpratap766@gmail.com; pgsql-bugs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
2020-06-01 13:52 BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) PG Bug reporting form <noreply@postgresql.org>
2020-06-02 06:20 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Kyotaro Horiguchi <horikyota.ntt@gmail.com>
@ 2020-06-02 22:09 ` Dave Cramer <davecramer@postgres.rocks>
2020-06-02 23:31 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Brajendra Pratap Singh <singh.bpratap766@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Dave Cramer @ 2020-06-02 22:09 UTC (permalink / raw)
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>; +Cc: singh.bpratap766@gmail.com; pgsql-bugs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
2020-06-01 13:52 BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) PG Bug reporting form <noreply@postgresql.org>
2020-06-02 06:20 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Kyotaro Horiguchi <horikyota.ntt@gmail.com>
2020-06-02 22:09 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Dave Cramer <davecramer@postgres.rocks>
@ 2020-06-02 23:31 ` Brajendra Pratap Singh <singh.bpratap766@gmail.com>
2020-06-03 01:15 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Dave Cramer <davecramer@postgres.rocks>
0 siblings, 1 reply; 5+ messages in thread
From: Brajendra Pratap Singh @ 2020-06-02 23:31 UTC (permalink / raw)
To: Dave Cramer <davecramer@postgres.rocks>; +Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>; pgsql-bugs@lists.postgresql.org
Hi,
Thanks for ur response.
Could you plz let me know ,what cause this error "Marked as broken because
of SQLSTATE(08006),ErrorCode(0)" .
Thanks,
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 anything
>
>
> Dave Cramer
> www.postgres.rocks
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0)
2020-06-01 13:52 BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) PG Bug reporting form <noreply@postgresql.org>
2020-06-02 06:20 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Kyotaro Horiguchi <horikyota.ntt@gmail.com>
2020-06-02 22:09 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Dave Cramer <davecramer@postgres.rocks>
2020-06-02 23:31 ` Re: BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) Brajendra Pratap Singh <singh.bpratap766@gmail.com>
@ 2020-06-03 01:15 ` Dave Cramer <davecramer@postgres.rocks>
0 siblings, 0 replies; 5+ messages in thread
From: Dave Cramer @ 2020-06-03 01:15 UTC (permalink / raw)
To: Brajendra Pratap Singh <singh.bpratap766@gmail.com>; +Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>; pgsql-bugs@lists.postgresql.org
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
>
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2020-06-03 01:15 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-06-01 13:52 BUG #16473: Marked as broken because of SQLSTATE(08006),ErrorCode(0) PG Bug reporting form <noreply@postgresql.org>
2020-06-02 06:20 ` Kyotaro Horiguchi <horikyota.ntt@gmail.com>
2020-06-02 22:09 ` Dave Cramer <davecramer@postgres.rocks>
2020-06-02 23:31 ` Brajendra Pratap Singh <singh.bpratap766@gmail.com>
2020-06-03 01:15 ` Dave Cramer <davecramer@postgres.rocks>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox