Tom Lane writes:
>Hans Buschmann writes:
>> This inspired me to propose dropping 32bit support for PostgreSQL starting
>> with PG17.
>I don't think this is a great idea. Even if Intel isn't interested,
>there'll be plenty of 32-bit left in the lower end of the market
>(think ARM, IoT, and so
On Thu, May 25, 2023 at 12:34 PM Tom Lane wrote:
> Dunno about antique MIPS. I think there's still some interest in
> not-antique 32-bit MIPS; I have some current-production routers
> with such CPUs. (Sadly, they don't have enough storage to do
> anything useful with, or I'd think about repurpos
Hi,
On 2023-05-24 20:34:38 -0400, Tom Lane wrote:
> Thomas Munro writes:
> > On Thu, May 25, 2023 at 11:51 AM Tom Lane wrote:
> >> You'll no doubt be glad to hear that I'll be retiring chickadee
> >> in the very near future.
>
> > . o O { I guess chickadee might have been OK anyway, along with e
Andres Freund writes:
> On 2023-05-24 19:51:22 -0400, Tom Lane wrote:
>> So dropping PA-RISC altogether should probably happen for v17, maybe even
>> v16.
> Definitely for 17 - not sure if we have much to gain by doing it in 16.
I'm just thinking that we'll have no way to test it. I wouldn't ad
Hi,
On 2023-05-24 19:51:22 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2023-05-24 17:44:36 -0400, Tom Lane wrote:
> >> Hmm, can we really expect atomic 8-byte reads on "relevant" 32-bit
> >> platforms? I'd be on board with this if so, but it sounds a bit
> >> optimistic.
>
> > ...
>
Thomas Munro writes:
> On Thu, May 25, 2023 at 11:51 AM Tom Lane wrote:
>> You'll no doubt be glad to hear that I'll be retiring chickadee
>> in the very near future.
> . o O { I guess chickadee might have been OK anyway, along with e.g.
> antique low-end SGI MIPS gear etc of "workstation"/"desk
On Thu, May 25, 2023 at 11:51 AM Tom Lane wrote:
> Andres Freund writes:
> > On 2023-05-24 17:44:36 -0400, Tom Lane wrote:
> > So it looks like the only certain problem is PA-RISC - which I personally
> > wouldn't include in "relevant" :), with some evaluation needed for 32bit
> > mips
> > and o
Andres Freund writes:
> On 2023-05-24 17:44:36 -0400, Tom Lane wrote:
>> Hmm, can we really expect atomic 8-byte reads on "relevant" 32-bit
>> platforms? I'd be on board with this if so, but it sounds a bit
>> optimistic.
> ...
> So it looks like the only certain problem is PA-RISC - which I pe
Hi,
On 2023-05-24 17:44:36 -0400, Tom Lane wrote:
> Andres Freund writes:
> > Dropping CPUs without native atomic operations / without a way to do
> > tear-free
> > 8 byte reads would make several substantial performance improvements easier,
> > while not really dropping any relevant platform.
>
On Wed, May 24, 2023 at 10:44:11AM -0400, Tom Lane wrote:
> Hans Buschmann writes:
> > This inspired me to propose dropping 32bit support for PostgreSQL starting
> > with PG17.
>
> I don't think this is a great idea. Even if Intel isn't interested,
> there'll be plenty of 32-bit left in the low
Andres Freund writes:
> Dropping CPUs without native atomic operations / without a way to do tear-free
> 8 byte reads would make several substantial performance improvements easier,
> while not really dropping any relevant platform.
Hmm, can we really expect atomic 8-byte reads on "relevant" 32-b
Hi,
On 2023-05-24 14:33:06 +, Hans Buschmann wrote:
> I recently stumbled over the following Intel proposal for dropping 32bit
> support in x86 processors. [1]
It's a proposal for something in the future. Which, even if implemented as is,
will affect future hardware, several years down the l
Hans Buschmann writes:
> This inspired me to propose dropping 32bit support for PostgreSQL starting
> with PG17.
I don't think this is a great idea. Even if Intel isn't interested,
there'll be plenty of 32-bit left in the lower end of the market
(think ARM, IoT, and so on).
I recently stumbled over the following Intel proposal for dropping 32bit
support in x86 processors. [1]
This inspired me to propose dropping 32bit support for PostgreSQL starting with
PG17.
It seems obvious that production systems mostly won't use newly installed 32
bit native code in late 2
14 matches
Mail list logo
