| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Ross <jross(at)wykids(dot)org>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Memory Usage and OpenBSD |
| Date: | 2010-01-28 07:33:26 |
| Message-ID: | dcc563d11001272333n46761ae9pda6f98acfd27b75f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 27, 2010 at 4:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> related to maximum per-process data space. I don't know BSD very well
> so I can't say if datasize is the only such value for BSD, but it'd be
> worth checking. (Hmm, on OS X which is at least partly BSDish, I see
> -m and -v in addition to -d, so I'm suspicious OpenBSD might have these
> concepts too.)
Isn't the usual advice here is to log the ulimit setting from the pg
startup script so you can what it really is for the user at the moment
they're starting up the db? (I think some guy named Tom mentioned
doing that before.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sun Duozhong (孙多忠) | 2010-01-28 07:48:02 | emedded SQL in C to get the record type from plpgsql |
| Previous Message | 张海峰 | 2010-01-28 07:32:06 | Function nesting issue |