Hi Scott,
It was the work_mem that was set too high. I reduced it to 32mb and the
function executed.
Just so I understand this. Every time a sort is performed within a function,
the sort memory is allocated, and then it not released until the function
completes? Rather then deallocating the me
On Fri, Mar 25, 2011 at 21:21, Merlin Moncure wrote:
> On Fri, Mar 25, 2011 at 3:26 AM, Erik Hesselink wrote:
>>> hm, ISTM (I don't know haskell) that the hdbc driver isn't doing any
>>> type of synchronization at all unless it is using a non thread safe
>>> libpq...and in that case it uses a glo
Hi. Your idea is cool - i think this feature ought to be added to
TODO. Sorted rows should be materialized when memory is exhaused, and
memory reused.
2011/3/26, Jeremy Palmer :
> Hi Scott,
>
> It was the work_mem that was set too high. I reduced it to 32mb and the
> function executed.
>
> Just so
Hello,
writing an extension library, I have a type only used to perform
efficient in-place aggregation, but absolutely not to be used as a
data type into a table (it contains pointers, so it would be a
guaranteed crash).
Is there a way to mark the type as non-storable?
Thanks,
-- Daniele
--
S
Daniele Varrazzo writes:
> Hello,
> writing an extension library, I have a type only used to perform
> efficient in-place aggregation, but absolutely not to be used as a
> data type into a table (it contains pointers, so it would be a
> guaranteed crash).
> Is there a way to mark the type as non-
On Sat, Mar 26, 2011 at 10:35 PM, Tom Lane wrote:
> Daniele Varrazzo writes:
>> Hello,
>> writing an extension library, I have a type only used to perform
>> efficient in-place aggregation, but absolutely not to be used as a
>> data type into a table (it contains pointers, so it would be a
>> gua
