pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Kevin Murphy <murphy@genome.chop.edu>
Cc: pgsql-general@postgresql.org
Subject: Re: Drupal and PostgreSQL - performance issues?
Date: Tue, 14 Oct 2008 23:07:52 -0400
Message-ID: <8373.1224040072@sss.pgh.pa.us> (raw)
In-Reply-To: <87od1mbpsv.fsf@oxford.xeocode.com>
References: <2434A118-CEFA-43A9-BA88-006EC1F80326@hoegh.org>
	<200810122214.53558.uwe@oss4u.com>
	<20081013090228.248a665f@dawn.webthatworks.it>
	<e7e0a2570810131945x1bbf10b8r67c0ac2a340b436f@mail.gmail.com>
	<20081014114011.0ebe495a@dawn.webthatworks.it>
	<3250B5B6-B507-4E79-BAF0-E98B73E9FED9@hoegh.org>
	<Pine.GSO.4.64.0810140942010.28645@westnet.com>
	<48F4B3C2.1050805@genome.chop.edu>
	<Pine.GSO.4.64.0810141747240.5472@westnet.com>
	<87od1mbpsv.fsf@oxford.xeocode.com>

Gregory Stark <stark@enterprisedb.com> writes:
> Greg Smith <gsmith@gregsmith.com> writes:
>> DB2 has automatically updated the "shmmax" kernel
>> parameter from "33554432" to the recommended value "268435456".

> This seems like a bogus thing for an application to do though. The Redhat
> people seem happy with the idea but I'm pretty sure it would violate several
> Debian packaging rules.

FWIW, I don't think Red Hat would accept it either.

> ISTM the right way to make it go away is to allocate temporary files and mmap
> them instead of using sysv shared memory.

That's a non-starter unless you can point to a different kernel API that
(a) is as portable as SysV and (b) offers the same amount of assistance
towards preventing multiple postmasters in the same data directory.
See many, many previous discussions in -hackers.

			regards, tom lane

view thread (68+ messages)  latest in thread

Message-ID: <8373.1224040072@sss.pgh.pa.us>
Permalink:  ../8373.1224040072@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8373.1224040072@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, stark@enterprisedb.com, gsmith@gregsmith.com, murphy@genome.chop.edu, pgsql-general@postgresql.org
  Subject: Re: Drupal and PostgreSQL - performance issues?
  In-Reply-To: <8373.1224040072@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox