pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Dmitry Morozovsky <marck@rinet.ru>
Cc: Chris White (cjwhite) <cjwhite@cisco.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.4.5 file write issue
Date: Thu, 10 Mar 2005 23:41:29 -0500
Message-ID: <28582.1110516089@sss.pgh.pa.us> (raw)
In-Reply-To: <200503110321.j2B3Lee22234@candle.pha.pa.us>
References: <200503110321.j2B3Lee22234@candle.pha.pa.us>

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I am now thinking we need to make this "10" a GUC variable for just such
> cases.  This is not the first request for this.

At most it's the second or third request ... and this is hardly the only
repetitive disk hit in Postgres.  I can't get excited about it.

			regards, tom lane



view thread (10+ messages)  latest in thread

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

 · 

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-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, marck@rinet.ru, cjwhite@cisco.com
  Subject: Re: 7.4.5 file write issue
  In-Reply-To: <28582.1110516089@sss.pgh.pa.us>
  References: <200503110321.j2B3Lee22234@candle.pha.pa.us> <28582.1110516089@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