On Fri, 2006-03-24 at 04:16, Jim C. Nasby wrote:
> On Thu, Mar 23, 2006 at 10:14:24AM +0100, Edoardo Serra wrote:
> > >Now, for the interesting test. Run the import on both machines, with
> > >the begin; commit; pairs around it. Halfway through the import, pull
> > >the power cord, and see which
On Thu, Mar 23, 2006 at 10:14:24AM +0100, Edoardo Serra wrote:
> >Now, for the interesting test. Run the import on both machines, with
> >the begin; commit; pairs around it. Halfway through the import, pull
> >the power cord, and see which one comes back up. Don't do this to
> >servers with data
At 18.44 21/03/2006, Scott Marlowe wrote:
Here's what's happening. On the "fast" machine, you are almost
certainly using IDE drives.
Oh yes, the fast machine has IDE drives, you got it ;)
Meanwhile, back in the jungle... The machine with IDE drives operates
differently. Most, if not all, I
On Tue, 2006-03-21 at 06:46, Edoardo Serra wrote:
> Hi all,
> I'm having a very strange performance
> problems on a fresh install of postgres 8.1.3
> I've just installed it with default option and
> --enable-thread-safety without tweaking config files yet.
>
> The import of a small SQL
The low end server by chance doesn't have an IDE disk that lies about
write completion, or a battery backed disk controller? Try disabling
fsync on the new server to get comparable figures.
Markus Bertheau
2006/3/21, Edoardo Serra <[EMAIL PROTECTED]>:
> Hi all,
> I'm having a very strang
Edoardo Serra writes:
> Hi all,
> I'm having a very strange performance problems on a fresh
> install of postgres 8.1.3
> I've just installed it with default option and --enable-thread-safety
> without tweaking config files yet.
>
> The import of a small SQL files into the DB (6 tables
