| From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ANALYZE after restore |
| Date: | 2002-04-03 01:52:45 |
| Message-ID: | Pine.LNX.4.21.0204031149210.7670-100000@linuxworld.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 3 Apr 2002, Christopher Kings-Lynne wrote:
> Hi,
>
> Would it be an idea to have pg_dump append an ANALYZE; command to the end of
> its dumps to assist newbies / inexperienced admins?
I do not think this is desired behaviour. Firstly, pg_dump is not just for
restoring data to the system. Presumably another flag would need to be
added to pg_dump to prevent an ANALYZE being appended. This is messing
and, in my opinion, it goes against the 'does what it says it does' nature
of Postgres. Secondly, in experienced admins are not going to get
experienced with database management unless they see that their database
runs like a dog and they have to read the manual.
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Proctor | 2002-04-03 02:50:52 | 16 parameter limit |
| Previous Message | Neil Conway | 2002-04-03 01:51:47 | Re: ANALYZE after restore |