| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | jim(at)nasby(dot)net |
| Cc: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>, Martin Foster <martin(at)ethereal-realms(dot)org>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Performance on OpenBSD |
| Date: | 2003-05-20 00:50:31 |
| Message-ID: | m3k7cm5tm0.fsf@varsoon.wireboard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Jim C. Nasby" <jim(at)nasby(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joseph Shraibman | 2003-05-20 01:02:06 | sequence caches |
| Previous Message | Larry Rosenman | 2003-05-20 00:33:49 | Re: pg_atoi problem with 7.3.2 |