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@noris.de | ICQ: 20193661
The quote was selected randomly. Really. | http://smurf.noris.de/
--
Statistics: Nubers looking for an argument.