| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Alex Hunsaker <badalex(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Setting oom_adj on linux? |
| Date: | 2010-01-08 22:38:22 |
| Message-ID: | 14771.1262990302@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> The other issue was with a Debian-specific patch which was applied to
> OpenSSH which basically just created noise in the log file, bug report
> here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487325
Hmm, that's pretty interesting, specifically this:
: After some discussion with the Linux-Vserver folks, they found some
: interesting information I thought it worth adding. First EPERM is not
: the error that they expected, and that inside a vserver guest its really
: strict about what options you open it with, both O_CREAT and O_TRUNC are
: forbidden, and O_WRONLY lets you write 0\n to it.
That suggests it might be worth our trouble to use open/write rather
than fopen, so that we can ensure the flags are correct to avoid this
type of restriction.
But in any case the main takeaway seems to be to not insist on the
operation succeeding ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2010-01-08 23:07:14 | Re: Serializable Isolation without blocking |
| Previous Message | Stephen Frost | 2010-01-08 22:24:06 | Re: Setting oom_adj on linux? |