| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Michael Paesold <mpaesold(at)gmx(dot)at> |
| Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: pg_autovacuum vacuum cost variables patch |
| Date: | 2004-10-26 13:38:59 |
| Message-ID: | 417E5373.4060907@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Michael Paesold wrote:
> Matthew T. O'Connor wrote:
>
>> Two questions:
>> 1) It is my understanding that these new GUC vars only effect vacuum.
>> That is they do NOT have any effect on an analyze command right? (I ask
>> since I'm only setting the vars before I issue a vacuum command)
>
>
> No, vacuum also affects analyze alone (cvs tip here):
> (2.5 seconds -> 50 seconds)
>
> [snip examples...]
> I suggest you also issue the SET commands for analyze also. ISTM that
> there is also no distinction between VACUUM and VACUUM FULL, but I
> think pg_autovacuum never does a vacuum full, so there is no problem
> with that.
Ok, I'll do that too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-10-26 14:47:40 | Re: Possible make_oidjoins_check Security Issue |
| Previous Message | Matthew T. O'Connor | 2004-10-26 13:37:34 | Re: pg_autovacuum vacuum cost variables patch |