| From: | Stefan Blanke <stefan(dot)blanke(at)framestore(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | ERROR: invalid memory alloc request size 1073741824 |
| Date: | 2018-01-30 17:35:23 |
| Message-ID: | 733ecd96-48ed-8d49-15e1-413eb535c4c6@framestore.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
We've tripped over an error when doing a "COPY.. TO STDOUT WITH BINARY"
query.
"ERROR: invalid memory alloc request size 1073741824"
(exactly 1GB)
So a palloc() call is failing on the AllocSizeIsValid() check.
Does anyone know if this a safety catch we are tripping with a bad query
- or whether this check is something that should never be hit (i.e. a bug).
This has been some discussion before about making a change before the
9.5beta1:
postgresql 9.5.4 (2PGDG.rhel6)
work_mem = 256MB
Thanks,
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-01-30 17:48:50 | Re: Alter view with dependence without drop view! |
| Previous Message | Adrian Klaver | 2018-01-30 17:07:06 | Re: pgAdmin 4 loading shapefiles |