From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Michael Akinde <michael(dot)akinde(at)met(dot)no> |
Subject: | Re: VACUUM FULL out of memory |
Date: | 2008-01-08 17:33:34 |
Message-ID: | 10838.1199813614@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Tue, Jan 08, 2008 at 05:27:16PM +0100, Michael Akinde wrote:
>> Those are the ulimits of the db_admin account (i.e., the user that set
>> up and runs the DB processes). Is Postgres limited by other settings?
> Are you sure?
> On one system I used many years ago, /bin/sh wasn't what I thought it was,
> and so the ulimit that I got when logged in was not what the postmaster was
> starting under. Took me many days to figure out what was up.
The only thing I find convincing is to insert "ulimit -a >someplace"
into the script that starts the postmaster, adjacent to where it does
so, and then reboot. There are too many systems on which daemons are
launched under settings different from what interactive shells use
(a policy that's often a good one, too).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2008-01-08 17:53:28 | Re: VACUUM FULL out of memory |
Previous Message | Cédric Villemain | 2008-01-08 17:32:51 | Re: 8.3.0 release schedule (Was:Re: [BUGS] BUG #3852: Could not create complex aggregate) |