Re: [HACKERS] /proc/self/oom_adj is deprecated in newer Linux kernels

2014-07-02 Thread Jonathan Corbet
On Tue, 1 Jul 2014 15:57:25 -0400 Robert Haas wrote: > Of course, we have no guarantee that the Linux kernel guys won't > change this again. Apparently "we don't break userspace" is a > somewhat selectively-enforced principle. It's selectively enforced in that kernel developers don't (and can't

Re: [HACKERS] [Lsf-pc] Linux kernel impact on PostgreSQL performance

2014-01-14 Thread Jonathan Corbet
On Wed, 15 Jan 2014 09:23:52 +1100 Dave Chinner wrote: > It appears to me that we are seeing large memory machines much more > commonly in data centers - a couple of years ago 256GB RAM was only > seen in supercomputers. Hence machines of this size are moving from > "tweaking settings for superco

[HACKERS] Fw: LSF/MM 2014 Call For Proposals

2013-12-20 Thread Jonathan Corbet
During the direct I/O discussion I'd suggested that somebody from the PostgreSQL community might want to put in an appearance at the LSFMM summit in March. Here's the CFP. My guess is that a proposal for a session on avoiding performance regressions for systems like PostgreSQL, probably crossing

Re: [HACKERS] Why we are going to have to go DirectIO

2013-12-04 Thread Jonathan Corbet
On Wed, 04 Dec 2013 13:01:37 -0800 Josh Berkus wrote: > > Perhaps even better: the next filesystem, storage, and memory management > > summit is March 24-25. > > Link? I can't find anything Googling by that name. I'm pretty sure we > can get at least one person there. It looks like the page

Re: [HACKERS] Why we are going to have to go DirectIO

2013-12-04 Thread Jonathan Corbet
On Wed, 04 Dec 2013 11:07:04 -0800 Josh Berkus wrote: > On 12/04/2013 07:33 AM, Jonathan Corbet wrote: > > Wow, Josh, I'm surprised to hear this from you. > > Well, I figured it was too angry to propose for an LWN article. ;-) So you're going to make us write it f

Re: [HACKERS] Why we are going to have to go DirectIO

2013-12-04 Thread Jonathan Corbet
On Tue, 03 Dec 2013 10:44:15 -0800 Josh Berkus wrote: > It seems clear that Kernel.org, since 2.6, has been in the business of > pushing major, hackish, changes to the IO stack without testing them or > even thinking too hard about what the side-effects might be. This is > perhaps unsurprising g

Re: [HACKERS] Deriving release notes from git commit messages

2011-06-27 Thread Jonathan Corbet
On Fri, 24 Jun 2011 13:42:04 -0400 Robert Haas wrote: > As for annotating the commit messages, I think something like: > > Reporter: Sam Jones > Author: Beverly Smith > Author: Jim Davids > Reviewer: Fred Block > Reviewer: Pauline Andrews Can I just toss in one little note from the sidelines?

Re: [HACKERS] Report: Linux huge pages with Postgres

2010-11-29 Thread Jonathan Corbet
nvolved if you'd like to experiment with this feature and see what it can do for you. jon Jonathan Corbet / LWN.net / cor...@lwn.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] antisocial things you can do in git (but not CVS)

2010-07-21 Thread Jonathan Corbet
On Wed, 21 Jul 2010 15:11:41 -0400 Andrew Dunstan wrote: > We have a clear idea of what should be part of the public history > contained in the authoritative repo and what should be history that is > private to the developer/tester/committer. We don't want to pollute the > former with the latt

Re: [HACKERS] antisocial things you can do in git (but not CVS)

2010-07-21 Thread Jonathan Corbet
On Tue, 20 Jul 2010 14:34:20 -0400 Robert Haas wrote: > I have some concerns related to the upcoming conversion to git and how > we're going to avoid having things get messy as people start using the > new repository. Here's a few responses from the point of view of somebody who has been working