| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rob Fielding <rob(at)dsvr(dot)net> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PG 7.2.4 and waiting backends |
| Date: | 2004-03-31 05:45:31 |
| Message-ID: | 29322.1080711931@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Rob Fielding <rob(at)dsvr(dot)net> writes:
> The intention is to migrate the DB from 7.2 to a later version. The
> interim has been to get up to the latest 7.2.4 release inorder to
> circumvent a vacuumdb corner case which was resulting in a FULL failing.
Hmm ... why do you feel that you have to do a VACUUM FULL before you
can dump and reload to go to a later version? AFAICS a vacuum in such a
context is just a waste of cycles. It's certainly not going to reduce
the size of the dump.
The problems you are describing sound like index bloat to me. If the
real issue is you haven't got enough disk space to do the dump, I'd
suggest dropping all your indexes, after making notes so you can
recreate them after finishing the upgrade.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2004-03-31 15:56:05 | Re: Spontaneous PostgreSQL Server Reboot? |
| Previous Message | Sam Barnett-Cormack | 2004-03-31 00:59:32 | Re: Accessing Linux Postgre Server from windows client |