Re: v16dev: invalid memory alloc request size 8488348128

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: v16dev: invalid memory alloc request size 8488348128
Date: 2023-04-15 01:20:01
Message-ID: CAApHDvofDJMp+=nRg0kqML2sQb1q_rD7oAecZUF+d-FtBXYtOQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 15 Apr 2023 at 13:03, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> Maybe you'll find valgrind errors to be helpful.

I don't think that's really going to help. The crash already tells us
there's a problem down the line, but if the commit you mention is to
blame for this, then the problem is elsewhere, either in our
assumption that we can get away without the datumCopy() or in the
aggregate function producing the state that we're no longer copying.

David

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-04-15 02:06:25 Re: Tab completion for CREATE SCHEMAAUTHORIZATION
Previous Message vignesh C 2023-04-15 01:08:59 Re: Support logical replication of DDLs