Re: Postgres 7.3.1 poor insert/update/search performance

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Curt Sampson <cjs(at)cynic(dot)net>, Neil Conway <neilc(at)samurai(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres 7.3.1 poor insert/update/search performance
Date: 2003-02-02 19:31:30
Message-ID: 200302021131.30209.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Curt,

> (MS SQL Server on Windows NT is a notable exception to this. They do,
> however, make you pre-create the data file in advance, and they suggest
> doing it on an empty partition, which at the very least would get you
> long stretches of the file in contiguous order. They may also be using
> tricks to make sure the file gets created in contiguous order, or they
> may be able to get information from the OS about the physical block
> numbers corresponding to logical block numbers in the file.)

MSSQL is, in fact, doing some kind of direct-block-addressing. If you
attempt to move a partition on the disk containing MSSQL databases, SQL
Server will crash on restart and be unrecoverable ... even if the other files
on that disk are fine. Nor can you back up MSSQL by using disk imaging,
unless you can recover to an identical model disk/array.

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Bruce Momjian 2003-02-03 00:41:00 Re: Postgres 7.3.1 poor insert/update/search performance
Previous Message alien 2003-02-02 18:09:29 Re: 1 char in the world