Re: Invalid memory alloc - Mailing list pgsql-general

From Marc-André Goderre
Subject Re: Invalid memory alloc
Date
Msg-id D8DAC91BA6256246BA3FF835F6AAA118994400C9@SI-MB01.cegep-chicoutimi.qc.ca
Whole thread Raw
In response to Re: Invalid memory alloc  (Chris Mair <chris@1006.org>)
Responses Re: Invalid memory alloc
List pgsql-general
Can I change the segment size to allow more memory?
Is it a good idea?
The concerned function work only on the entire table then I can't process a part of it.
Should I split the table in multiple table and merge them after the process?

Thanks
Marc




-----Message d'origine-----
De : Chris Mair [mailto:chris@1006.org] 
Envoyé : 24 avril 2015 15:41
À : Marc-André Goderre; pgsql-general@postgresql.org
Objet : Re: [GENERAL] Invalid memory alloc

> I use Postgis and PGrouting extension.
> The error come when I use a pgrouting function pgr_createtopology()

It appears pgrouting violates the 1GB per chunk limit in the postgres backend when processing large datasets:

https://github.com/pgRouting/pgrouting/issues/291

Bye,
Chris.



pgsql-general by date:

Previous
From: Evan Martin
Date:
Subject: Workaround for bug #13148 (deferred EXCLUDE constraint violation)
Next
From: Jim Nasby
Date:
Subject: Re: Invalid memory alloc