Re: [HACKERS] Why is that so slow?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: t-ishii(at)sra(dot)co(dot)jp, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Why is that so slow?
Date: 1999-03-07 11:27:54
Message-ID: 199903071127.GAA15132@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> >> Something is fishy here. Have you done a "vacuum analyze" since loading
> >> the data in these tables?
>
> > Oh, I never thought about that.
>
> Ah. OK, that explains the system's poor choice of plan --- it was
> effectively operating on the assumption that these tables were small.
>
> (Note to hackers: maybe a freshly created table should be given dummy
> statistics, say having 1000 rows instead of 0 rows? That would help
> to prevent the optimizer from making really foolish choices when no
> vacuum's been done yet for the table. But I dunno whether we could
> invent plausible default values for all the stats...)

No way to really make a default. Zero is the correct number when the
table is created, right? Improved optimize may be even worse or better
for un-analyzed tables.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-03-07 11:51:03 Re: [HACKERS] Re: Max backend limits cleaned up
Previous Message Kevin Lo 1999-03-07 04:53:20 Re: [HACKERS] int 8 on FreeBSD