Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jimmy Yih <jyih(at)pivotal(dot)io>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket
Date: 2018-07-19 20:48:13
Message-ID: 20180719204812.GR9712@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 19, 2018 at 01:46:12PM -0700, Andres Freund wrote:
> On 2018-07-19 15:42:46 -0500, Nico Williams wrote:
> > Yes, but that's in libc. None of that is in the PG code itself.
>
> That's simply entirely completely wrong. PG has a good chunk of memory
> management layers (facilitating memory contexts) ontop of malloc. And
> that's stateful.

Ah, Ok, I see. Fine.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2018-07-19 21:43:49 Re: [HACKERS] advanced partition matching algorithm for partition-wise join
Previous Message Andres Freund 2018-07-19 20:47:06 Re: [HACKERS] possible self-deadlock window after bad ProcessStartupPacket