Re: Performance (was: The New Slashdot Setup (includes MySql server))

From: "Matthias Urlichs" <smurf(at)noris(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthias Urlichs" <smurf(at)noris(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance (was: The New Slashdot Setup (includes MySql server))
Date: 2000-05-20 08:09:00
Message-ID: 20000520100900.H27730@noris.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Hi,

Tom Lane:
> It never pays to assume you know what's happening without having looked
> :-(. It turns out the planner is not the only culprit: the executor's
> ExecOpenIndices() routine *also* does a sequential scan of pg_index.

That meshes with my observation that updates seem to do twice as many
read() calls on pg_index than inserts.

For this test, anyway.

--
Matthias Urlichs | noris network GmbH | smurf(at)noris(dot)de | ICQ: 20193661
The quote was selected randomly. Really. | http://smurf.noris.de/
--
Statistics: Nubers looking for an argument.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Dustin Sallings 2000-05-20 08:16:16 Re: Performance
Previous Message Mike Mascari 2000-05-20 07:06:08 Re: bool and NOT

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris 2000-05-20 08:29:12 Re: OO Patch
Previous Message Matthias Urlichs 2000-05-20 08:03:03 Re: Re: Heaps of read() syscalls by the postmaster