I was a little busy with deadlines at the time but I saved the database
in it's slow configuration so I could investigate during a quieter period.
I'll do a restore now and see whether I can remember back to April when
I came across this issue.
Pete
Tom Lane wrote:
Peter Wilson <petew@xxxxxxxxxxxxxxxx> writes:
I found a while ago that after inserting a lot of rows into a clean
Postgres table it would take several minutes just to analyse a command,
not even starting the execution.
Oh? Could you provide a test case for this? I can certainly believe
that the planner might choose a bad plan if it has no statistics, but
it shouldn't take a long time to do it.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
