| From: | Marc-André Goderre <magoderre(at)cgq(dot)qc(dot)ca> |
|---|---|
| To: | Chris Mair <chris(at)1006(dot)org>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Invalid memory alloc |
| Date: | 2015-04-27 13:45:01 |
| Message-ID: | D8DAC91BA6256246BA3FF835F6AAA118994400C9@SI-MB01.cegep-chicoutimi.qc.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)1006(dot)org]
Envoyé : 24 avril 2015 15:41
À : Marc-André Goderre; pgsql-general(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-04-27 21:34:02 | Re: Invalid memory alloc |
| Previous Message | Roger Pack | 2015-04-27 13:07:06 | Re: Fwd: [GENERAL] 4B row limit for CLOB tables |