From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Anton Maksimenkov <anton200(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Jeff Ross <jross(at)wykids(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Memory Usage and OpenBSD |
Date: | 2010-02-09 10:38:40 |
Message-ID: | dcc563d11002090238l2c512ffen541e66034c74186a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Feb 9, 2010 at 3:18 AM, Anton Maksimenkov <anton200(at)gmail(dot)com> wrote:
> 2010/1/28 Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>:
>>> 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.)
>
> I think that "su" is enough:
In previous discussions it was mentioned that startup scripts often
inherit different settings from the default shell of a user, hence the
need to check it from within the startup script.
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2010-02-09 11:07:02 | dynamic plpgsql command on a record type |
Previous Message | Fredric Fredricson | 2010-02-09 10:21:24 | Re: Order by and strings |