pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vivek Khera <khera@kcilink.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Subject: Re: checkpoints too frequent
Date: Fri, 5 Sep 2003 11:41:53 -0400
Message-ID: <16216.44737.326214.974984@yertle.int.kciLink.com> (raw)
In-Reply-To: <200309051517.h85FHZw25603@candle.pha.pa.us>
References: <x7he3vb2nn.fsf@yertle.int.kciLink.com>
	<200309051517.h85FHZw25603@candle.pha.pa.us>

>>>>> "BM" == Bruce Momjian <pgman@candle.pha.pa.us> writes:

BM> Vivek, you reported recently that increasing sort_mem and
BM> checkpoint_segments increased performance.  Can you run a test to see
BM> how much of that improvement was just because of increasing
BM> checkpoint_segments?

i was thinking just the same thing myself.

i'll start that run now.



view thread (2+ messages)

Message-ID: <16216.44737.326214.974984@yertle.int.kciLink.com>
Permalink:  ../16216.44737.326214.974984@yertle.int.kciLink.com/
Also on:    postgresql.org/message-id/16216.44737.326214.974984@yertle.int.kciLink.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: khera@kcilink.com, pgman@candle.pha.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: checkpoints too frequent
  In-Reply-To: <16216.44737.326214.974984@yertle.int.kciLink.com>
  References: <x7he3vb2nn.fsf@yertle.int.kciLink.com> <200309051517.h85FHZw25603@candle.pha.pa.us> <16216.44737.326214.974984@yertle.int.kciLink.com>

* 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