From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: COPY into table too slow with index: now an I/O
Date: Fri, 02 Dec 2005 08:04:19 -0500
Message-ID: <20051202130419.GF7330@mathom.us> (raw)
In-Reply-To: <3E37B936B592014B978C4415F90D662D01C48EFB@MI8NYCMAIL06.Mi8.com>
References: <3E37B936B592014B978C4415F90D662D01C48EFB@MI8NYCMAIL06.Mi8.com>
On Fri, Dec 02, 2005 at 12:15:57AM -0500, Luke Lonergan wrote:
>That's good to know - makes sense. I suppose we might still thrash over
>a 1GB range in seeks if the BG writer starts running at full rate in the
>background, right? Or is there some write combining in the BG writer?
That part your OS should be able to handle. Those writes aren't synced,
so the OS has plenty of opportunity to buffer & aggregate them.
Mike Stone
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: mstone+postgres@mathom.us
Subject: Re: COPY into table too slow with index: now an I/O
In-Reply-To: <20051202130419.GF7330@mathom.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