I've had a look at the documentation for how much shared memory (in bytes)
Postgres uses:
http://www.postgresql.org/docs/8.4/static/kernel-resources.html#SHARED-MEMORY-PARAMETERS
However, after using these calculations to work out the shared memory usage
for my own setup, the numbers I came up with
Thom Brown writes:
> I've had a look at the documentation for how much shared memory (in bytes)
> Postgres uses:
> http://www.postgresql.org/docs/8.4/static/kernel-resources.html#SHARED-MEMORY-PARAMETERS
> However, after using these calculations to work out the shared memory usage
> for my own set
2009/10/10 Tom Lane
> Thom Brown writes:
> > I've had a look at the documentation for how much shared memory (in
> bytes)
> > Postgres uses:
> >
> http://www.postgresql.org/docs/8.4/static/kernel-resources.html#SHARED-MEMORY-PARAMETERS
> > However, after using these calculations to work out the
Thom Brown writes:
> 2009/10/10 Tom Lane
>> Clearly wrong compared to what --- ie, what's the actual size of your
>> shared memory segment? (See ipcs)
> I don't actually know the size of my shared memory segment. "sysctl -a |
> grep -i shmseg" doesn't return anything as it hasn't been set, and
2009/10/10 Tom Lane
>
> There is no "default value", we are talking about the actual size of an
> actual memory object. Which you find out with ipcs, not sysctl.
> For instance
>
> $ ipcs -a
>
> -- Shared Memory Segments
> keyshmid owner perms bytes nattc
Thom Brown writes:
> My mistake. I've never seen that before. Running it on mine returns the
> following:
> -- Shared Memory Segments
> keyshmid owner perms bytes nattch status
> 0x0052e2c1 491520 postgres 600235511808 4
Okay, so your
