Re: [multithreading] extension compatibility

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tristan Partin <tristan(at)partin(dot)io>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: [multithreading] extension compatibility
Date: 2024-06-06 14:32:12
Message-ID: 7a67170e-b3bd-427a-87d3-70bc60cab5f9@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/06/2024 17:23, Robert Haas wrote:
> On Thu, Jun 6, 2024 at 5:00 AM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> If there is some material harm from compiling with multithreading
>> support even if you're not using it, we should try to fix that. I'm not
>> dead set against having a compile-time option, but I don't see the need
>> for it at the moment.
>
> Well, OK, so it sounds like I'm outvoted, at least at the moment.
> Maybe that will change as more people vote, but for now, that's where
> we are. Given that, I suppose we want something more like Tristan's
> patch, but with a more extensible syntax. Does that sound right?

+1

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-06-06 14:34:07 report on not thread-safe functions
Previous Message Robert Haas 2024-06-06 14:29:59 Re: Things I don't like about \du's "Attributes" column