On Wed, 2005-03-23 at 14:22 -0500, Keith Browne wrote:
Simon Riggs wrote:
The EXPLAINs you've enclosed are for SELECTs, yet your bug report
describes INSERTs as being the things that are slow.
[You may find better performance from using COPY]
We're starting with an empty database,
Simon Riggs [EMAIL PROTECTED] writes:
I think we should spawn a TODO item from this:
* Coerce FK lookups to always use an available index
No, we aren't doing that.
The correct TODO item is Replan cached plans when table size has
changed a lot which of course depends on having a framework to do
