| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: Is stats update during COPY IN really a good idea? |
| Date: | 2001-05-22 07:19:53 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633682E5@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We have a TODO item
> * Update reltuples in COPY
>
> I was just about to go do this when I realized that it may not be such
> a hot idea after all.
Imho it is not a good idea at all. The statistics are a very sensitive area,
that imho should only be calculated on request. I already don't like the
statistics that are implicitly created during create index.
Eighter you have online stats keeping or you don't.
For me this is a definite all or nothing issue. Anything inbetween is
only good for unpleasant surprises.
I have very strong feelings about this, because of bad experience.
I would be willing to go into detail.
A syntactic extension to copy ("with analyze") on the other hand would
be a feature.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denis Perchine | 2001-05-22 07:25:59 | Re: Re: AW: Plans for solving the VACUUM problem |
| Previous Message | Christopher Kings-Lynne | 2001-05-22 06:25:40 | RE: DROP CONSTRAINT patch |