On Mon, June 30, 2008 9:45 pm, Tom Lane wrote:
> "Henry - Zen Search SA" <[EMAIL PROTECTED]> writes:
>> The problem was this: a silly SQL error (misuse of OR and missing
>> parentheses) resulted in a massive result set which resulted in OOM - if
>> the select is run manually (no funny "out of bala
"Henry - Zen Search SA" <[EMAIL PROTECTED]> writes:
> The problem was this: a silly SQL error (misuse of OR and missing
> parentheses) resulted in a massive result set which resulted in OOM - if
> the select is run manually (no funny "out of balance" strings).
> If it's run in a function (which u
On Mon, June 30, 2008 4:51 pm, Tom Lane wrote:
> The string "out of balance" appears nowhere in the PG 8.2.x sources.
> So I suppose it must have come from some add-on code, or perhaps got
> inserted on the client side. What data type is that column, and what
> non-core code is involved?
I have n
"Henry - Zen Search SA" <[EMAIL PROTECTED]> writes:
> Our selects which have run normally for a very long time suddenly started:
> - consuming all memory.
> - crashing (oom) if the select was run directly.
> - producing "out of balance" results in one of the column results if run
> from within a f
Hello,
PG: 8.2.7 (then upgraded to 8.2.9 to try and resolve with same result)
Linux 2.6.25
Our selects which have run normally for a very long time suddenly started:
- consuming all memory.
- crashing (oom) if the select was run directly.
- producing "out of balance" results in one of the colum
