Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id CA+hUKG+DSBxo+9=EkxuGz0t1s_s2im7wM+8Xg18iBn7rrbv_nQ@mail.gmail.com
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Andres Freund <andres@anarazel.de>)
Responses Re: seawasp failing, maybe in glibc allocator
List pgsql-hackers
On Mon, Jun 21, 2021 at 11:57 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> If that's an accurate characterization of the tradeoff, I have little
> difficulty in voting for #2.  A crash is strictly worse than a memory
> leak.  Besides which, I've heard little indication that they might
> revert.

Agreed.

On Mon, Jun 21, 2021 at 10:23 PM Andres Freund <andres@anarazel.de> wrote:
> I think I'd vote for 2 or 2+ (backpatch immediately).

Yeah, that makes sense.  Done.

Seawasp should turn green on its next run.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Pipeline mode and PQpipelineSync()
Next
From: Masahiko Sawada
Date:
Subject: Re: Transactions involving multiple postgres foreign servers, take 2