| From: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: VACUUM FULL out of memory |
| Date: | 2008-01-08 17:53:28 |
| Message-ID: | 20080108175328.GB11262@frubble.xen.chris-lamb.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 08, 2008 at 12:33:34PM -0500, Tom Lane wrote:
> Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> > 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).
What about a stored procedure in a language that allows you to do
system(3) calls?
Sam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-01-08 17:57:23 | Re: Proposal - libpq Type System beta-0.8a (was PGparam) |
| Previous Message | Tom Lane | 2008-01-08 17:33:34 | Re: VACUUM FULL out of memory |