> Could you adjust your process to log the actual temp table size
> each time, ie "select count(*) from temp_table" in between the
> two steps, and then note whether the failures are correlated
> with unusual temp table sizes?
Thanks, I'll add a count there and come back with a number when we nex
Stefan Blanke writes:
> We've upgraded to PostgreSQL 11.5 (postgresql.org rhel 6 rpm) and I have
> had another occurrence of this invalid alloc of 1GB. Apologies for never
> providing a query plan when discussing this two years ago; we decided to
> move to a newer PostgreSQL to see if the issue
Hi,
We've upgraded to PostgreSQL 11.5 (postgresql.org rhel 6 rpm) and I have
had another occurrence of this invalid alloc of 1GB. Apologies for never
providing a query plan when discussing this two years ago; we decided to
move to a newer PostgreSQL to see if the issue went away but took a
wh
On 01/31/2018 09:51 PM, Jan Wieck wrote:
>
>
> On Wed, Jan 31, 2018 at 12:32 PM, Stefan Blanke
> mailto:stefan.bla...@framestore.com>> wrote:
>
> >
> > I'll bet you it's not that. It's quite unlikely that would fail with
> > exactly 1GB request size. It seems much more like a buffe
;
> On 01/30/18 22:00, Tomas Vondra wrote:
>
>>
>>
>> On 01/30/2018 10:43 PM, Jan Wieck wrote:
>>
>>>
>>>
>>> On Tue, Jan 30, 2018 at 12:35 PM, Stefan Blanke
>>> mailto:stefan.bla...@framestore.com>>
>>> wrote:
30/2018 10:43 PM, Jan Wieck wrote:
On Tue, Jan 30, 2018 at 12:35 PM, Stefan Blanke
mailto:stefan.bla...@framestore.com>> wrote:
Hello,
We've tripped over an error when doing a "COPY.. TO STDOUT WITH
BINARY" query.
"ERROR: invalid memory alloc request si
On 01/30/2018 10:43 PM, Jan Wieck wrote:
>
>
> On Tue, Jan 30, 2018 at 12:35 PM, Stefan Blanke
> mailto:stefan.bla...@framestore.com>> wrote:
>
> Hello,
>
> We've tripped over an error when doing a "COPY.. TO STDOUT WITH
> BINARY&quo
On Tue, Jan 30, 2018 at 12:35 PM, Stefan Blanke <
stefan.bla...@framestore.com> wrote:
> Hello,
>
> We've tripped over an error when doing a "COPY.. TO STDOUT WITH BINARY"
> query.
>
> "ERROR: invalid memory alloc request size 1073741824"
> (
On 01/30/2018 06:35 PM, Stefan Blanke wrote:
> 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 i
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
10 matches
Mail list logo
