RE: [HACKERS] Some notes on optimizer cost estimates

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Subject: RE: [HACKERS] Some notes on optimizer cost estimates
Date: 2000-01-21 02:59:20
Message-ID: 001201bf63bb$83adc1a0$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> > In addition,vacuum error occurs with analyze option in most
> > cases AFAIK.
>
> Still, with current sources? What's the error message? I fixed
> a problem with pg_statistic tuples getting too big...
>

Sorry,my English is poor.
When I saw vacuum bug reports,there were 'analyze' option mostly.
'Analyze' is harmful for safety of vacuum.

I'm thinking that 'analyze' is not preferable especially for index
recreation in vacuum.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-01-21 03:10:28 Re: [HACKERS] Some notes on optimizer cost estimates
Previous Message Bruce Momjian 2000-01-21 02:48:57 Re: [HACKERS] Some notes on optimizer cost estimates