From: | Geoffrey Myers <lists(at)serioustechnology(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: out of memory error |
Date: | 2011-07-05 15:12:29 |
Message-ID: | 4E1329DD.9010408@serioustechnology.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Geoffrey Myers <geof(at)serioustechnology(dot)com> writes:
>> Geoffrey Myers wrote:
>>> out of memory for query result
>
>> One other note that is bothering me. There is no reference in the log
>> regarding the out of memory error. Should that not also show up in the
>> associated database log?
>
> Not if it's a client-side error.
>
> (Which a quick grep through the PG source code says it is ...)
>
> regards, tom lane
Wanted to add more specifics. Here is the actual code that generated the
error:
my $result = $conn->exec($select);
if ($result->resultStatus != PGRES_TUPLES_OK)
{
$error = $conn->errorMessage;
die "Error: <$error> Failed: <$select>";
}
So you're saying this select request failing would not be logged to the
postgres database log?
--
Until later, Geoffrey
"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Figueiredo Jr. | 2011-07-05 15:14:12 | Re: Pgfoundry problem with Npgsql bug tracker |
Previous Message | Tom Lane | 2011-07-05 15:05:20 | Re: out of memory error |