Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

> On Wed, 5 Oct 2022 at 16:30, Tom Lane wrote: > > One other point to discuss: should we consider back-patching? I've > > got mixed feelings about that myself. I don't think that cases where > > this helps significantly are at all mainstream, so I'm kind of leaning > > to "patch HEAD only". At

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

On Wed, 5 Oct 2022 at 16:30, Tom Lane wrote: > > Kyotaro Horiguchi writes: > > At Tue, 4 Oct 2022 17:15:31 -0700, Nathan Bossart > > wrote in > >> On Tue, Oct 04, 2022 at 07:53:11PM -0400, Tom Lane wrote: > >>> After further thought, maybe it'd be better to do it as attached, > >>> with one

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

On Wed, Oct 05, 2022 at 11:30:22AM -0400, Tom Lane wrote: > One other point to discuss: should we consider back-patching? I've > got mixed feelings about that myself. I don't think that cases where > this helps significantly are at all mainstream, so I'm kind of leaning > to "patch HEAD only".

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

Kyotaro Horiguchi writes: > At Tue, 4 Oct 2022 17:15:31 -0700, Nathan Bossart > wrote in >> On Tue, Oct 04, 2022 at 07:53:11PM -0400, Tom Lane wrote: >>> After further thought, maybe it'd be better to do it as attached, >>> with one long-lived hash table for all the locks. > First one is

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

At Tue, 4 Oct 2022 17:15:31 -0700, Nathan Bossart wrote in > On Tue, Oct 04, 2022 at 07:53:11PM -0400, Tom Lane wrote: > > I wrote: > >> PFA a quick-hack fix that solves this issue by making per-transaction > >> subsidiary hash tables. That's overkill perhaps; I'm a little worried > >> about

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

On Tue, Oct 04, 2022 at 07:53:11PM -0400, Tom Lane wrote: > I wrote: >> PFA a quick-hack fix that solves this issue by making per-transaction >> subsidiary hash tables. That's overkill perhaps; I'm a little worried >> about whether this slows down normal cases more than it's worth. >> But we

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

I wrote: > PFA a quick-hack fix that solves this issue by making per-transaction > subsidiary hash tables. That's overkill perhaps; I'm a little worried > about whether this slows down normal cases more than it's worth. > But we ought to do something about this, because aside from the >

Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records

[ redirecting to -hackers because patch attached ] David Rowley writes: > So that confirms there were 950k relations in the xl_standby_locks. > The contents of that message seem to be produced by standby_desc(). > That should be the same WAL record that's processed by standby_redo() > which adds

Re: ERROR: invalid memory alloc request size 1073741824

cropin_suhal: * *BEGIN* *CREATE TABLE* *ERROR: invalid memory alloc request size 1073741824* *ERROR: current transaction is aborted, commands ignored until end of transaction block* *ERROR: current transaction is aborted, commands ignored until end of transaction block* *ERROR: current transaction

Re: ERROR: invalid memory alloc request size 1073741824

Suhal Vemu writes: > so, i need to import the tif file of memory greater than 500mb at least . If you're trying to cram that into a single bytea field, it's unsurprising that it fails. PG is not designed to work with table rows (let alone individual fields) that

Re: ERROR: invalid memory alloc request size 1073741824

On 6 April 2018 at 22:06, Suhal Vemu <su...@cropextechnology.com> wrote: > ERROR: > BEGIN > CREATE TABLE > ERROR: invalid memory alloc request size 1073741824 Can we see the full CREATE TABLE command? Are you able to get the CREATE TABLE to succeed if you try removin