| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Markus Schaber <schabi(at)logix-tt(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [ADMIN] Vacuum error on database postgres |
| Date: | 2006-09-15 12:45:07 |
| Message-ID: | 87ac51qox8.fsf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Markus Schaber <schabi(at)logix-tt(dot)com> writes:
> Is there any reason to allow ANALYZE run insinde a transaction at all?
I had a script to run explain over a set of queries, then run analyze, then
run explain again and check the plans for unexpected changes. It would roll
back the analyze if any production queries had changed plans and email the
diff to the DBA to review.
Actually I never finished the script but that was the plan :)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Donald Fraser | 2006-09-15 12:47:21 | Odd behaviour with WAL and pg_stop_backup |
| Previous Message | Markus Schaber | 2006-09-15 12:44:28 | Re: [ADMIN] Vacuum error on database postgres |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Schoenen, Holger | 2006-09-15 13:07:00 | backup + restore fails |
| Previous Message | Markus Schaber | 2006-09-15 12:44:28 | Re: [ADMIN] Vacuum error on database postgres |