| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Neil Conway <neilc(at)samurai(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Row level stats |
| Date: | 2003-03-06 16:43:40 |
| Message-ID: | 1046969020.487.23.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2003-03-06 at 11:40, Neil Conway wrote:
> On Thu, 2003-03-06 at 09:16, Rod Taylor wrote:
> > Anyway, the basic proposal would be to change the on / off flags for row
> > & block level into a 'stats delay'. A large number would be off, 0
> > would have the same properties as today. Default to be determined (but
> > 1 second seems to be plenty).
>
> "A large number" seems messy. Why not "-1"? I also don't really like
> using "0" to mean "enabled", but I can't think of anything better...
>
> And the default should be to disable row-level stats, naturally.
Not if we expect pg_autovacuum to be able to work. It *needs* this
information. I really want an auto-vacuum in the backend, and figured
the first step was to fix stats so they don't have such a high cost.
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2003-03-06 16:47:11 | Re: Row level stats |
| Previous Message | Neil Conway | 2003-03-06 16:40:04 | Re: Row level stats |