From: | Ioannis Anagnostopoulos <ioannis(at)anatec(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Running analysis as part of a stored proc |
Date: | 2012-07-30 08:39:42 |
Message-ID: | 5016484E.3070206@anatec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 28/07/2012 21:00, Tom Lane wrote:
> Ioannis Anagnostopoulos <ioannis(at)anatec(dot)com> writes:
>> Is it advisable to include a VACUUM ANALYZE <table name> within a stored
>> procedure that runs as part of a batch every night?
> If you're envisioning this as cleanup after the day's activities,
> autovacuum will almost certainly make that unnecessary.
>
> The typical cases where you need a manual vacuum or analyze in a stored
> proc are where you need the cleanup or new stats immediately and can't
> wait for autovacuum to get around to it. So if this is a step in a
> process where you just modified the table heavily and you need the
> cleanup done before you get to the next step, then yes it'd make sense.
>
> regards, tom lane
>
Hi Tom and thank you. The second scenario is exactly what I had in my
mind. As the tables have
constant inserts, it might be a good idea to run the analyse just before
executing the night batch.
Kind Regards
Yiannis
From | Date | Subject | |
---|---|---|---|
Next Message | pg noob | 2012-07-30 13:48:38 | 8.4.12 log truncation not working? |
Previous Message | Tom Lane | 2012-07-28 20:00:58 | Re: Running analysis as part of a stored proc |