Re: PostgreSQL Performance on OpenBSD - Mailing list pgsql-general

From Doug McNaught
Subject Re: PostgreSQL Performance on OpenBSD
Date
Msg-id m3k7cm5tm0.fsf@varsoon.wireboard.com
Whole thread Raw
In response to Re: PostgreSQL Performance on OpenBSD  ("scott.marlowe" <scott.marlowe@ihs.com>)
Responses Re: PostgreSQL Performance on OpenBSD  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-general
"Jim C. Nasby" <jim@nasby.net> writes:

> Hmm... this could explain some of the memory alloc errors people have
> been posting about. It would be very useful if pgsql could limit the
> amount of memory used by a connection, or better yet, used across all
> connections. This way you could ensure that you never start swapping.

Per-connection is easy: 'man ulimit'

Across all connections is possible if your system supports per-user
limits (in addition to per-process) but otherwise all the bookkeeping
would have to be done in the server, kept in shared memory and managed
with a semaphore.  Somehow I doubt you'd get that patch accepted.  :)

-Doug

pgsql-general by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: pg_atoi problem with 7.3.2
Next
From: Joseph Shraibman
Date:
Subject: sequence caches