Re: SELECT INTO large FKyed table is slow

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Mario Splivalo" <mario(dot)splivalo(at)megafon(dot)hr>, "Mladen Gogala" <mladen(dot)gogala(at)vmsinfo(dot)com>
Cc: "jd(at)commandprompt(dot)com" <jd(at)commandprompt(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: SELECT INTO large FKyed table is slow
Date: 2010-12-01 17:24:35
Message-ID: 4CF63073020000250003802E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> wrote:

> There is a operating system which comes with a very decent extent
> based file system and a defragmentation tool, included in the OS.
> The file system is called "NTFS"

Been there, done that. Not only was performance quite poor compared
to Linux, but reliability and staff time to manage things suffered
in comparison to Linux.

We had the luxury of identical hardware and the ability to load
balance a web site with millions of hits per day evenly between them
in both environments, as well as off-line saturation load testing.
At least for running a PostgreSQL database, my experience suggests
that the only reasonable excuse for running database on a Windows
server is that you're under a mandate from ill-informed managers to
do so.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mladen Gogala 2010-12-01 17:33:27 Re: SELECT INTO large FKyed table is slow
Previous Message Kenneth Marshall 2010-12-01 17:22:08 Re: SELECT INTO large FKyed table is slow