pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeffrey W. Baker <jwbaker@acm.org>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Steve Poe <spoe@sfnet.cc>
Cc: Chris Browne <cbbrowne@acm.org>
Subject: Re: Read/Write block sizes
Date: Wed, 24 Aug 2005 01:10:20 -0400
Message-ID: <21415.1124860220@sss.pgh.pa.us> (raw)
In-Reply-To: <1124852854.11147.5.camel@noodles>
References: <d4b67d7c2b.d7c2bd4b67@bur-mail1.east.sun.com>
	<60k6icpapm.fsf@dba2.int.libertyrms.com>
	<1124846743.12045.94.camel@amd64-laptop-spoe>
	<200508231931.29682.josh@agliodbs.com>
	<1124852854.11147.5.camel@noodles>

"Jeffrey W. Baker" <jwbaker@acm.org> writes:
> To get decent I/O you need 1MB fundamental units all the way down the
> stack.

It would also be a good idea to have an application that isn't likely
to change a single bit in a 1MB range and then expect you to record
that change.  This pretty much lets Postgres out of the picture.

			regards, tom lane



view thread (24+ messages)  latest in thread

Message-ID: <21415.1124860220@sss.pgh.pa.us>
Permalink:  ../21415.1124860220@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/21415.1124860220@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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, jwbaker@acm.org, josh@agliodbs.com, spoe@sfnet.cc, cbbrowne@acm.org
  Subject: Re: Read/Write block sizes
  In-Reply-To: <21415.1124860220@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