Re: Decrease MAX_BACKENDS to 2^16 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Decrease MAX_BACKENDS to 2^16
Date
Msg-id 21832.1398525759@sss.pgh.pa.us
Whole thread Raw
In response to Re: Decrease MAX_BACKENDS to 2^16  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Decrease MAX_BACKENDS to 2^16  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-04-26 05:40:21 -0700, David Fetter wrote:
>> Out of curiosity, where are you finding that a 32-bit integer is
>> causing problems that a 16-bit one would solve?

> Save space? For one it allows to shrink some structs (into one
> cacheline!).

And next week when we need some other field in a buffer header,
what's going to happen?  If things are so tight that we need to
shave a few bits off backend IDs, the whole thing is a house of
cards anyway.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Decrease MAX_BACKENDS to 2^16
Next
From: Greg Stark
Date:
Subject: Re: Problem with displaying "wide" tables in psql