pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Dump/Restore vs Vacuum Full
3+ messages / 2 participants
[nested] [flat]

* Dump/Restore vs Vacuum Full
@ 2004-09-02 00:59 Adi Alurkar <adi@sf.net>
  2004-09-03 17:03 ` Re: Dump/Restore vs Vacuum Full Adi Alurkar <adi@sf.net>
  0 siblings, 1 reply; 3+ messages in thread

From: Adi Alurkar @ 2004-09-02 00:59 UTC (permalink / raw)
  To: pgsql-admin

Greetings,

Are there any differences, advantages of running a dump/restore vs 
running the following:1)REINDEX all the tables in all the databases, 
2)VACUUM FULL ANALYZE on all the databases

Assuming the following
1) the system can be offline.
2) PG version 7.4.x
3) pg_autovacuum running as a daemon with 30 minutes sleep but have had 
a few occasions where pg_autovacuum had to be killed and restarted.
4) FSM settings are set > than required by VACUUM ANALYZE VERBOSE 
"test".

-Adi




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Dump/Restore vs Vacuum Full
  2004-09-02 00:59 Dump/Restore vs Vacuum Full Adi Alurkar <adi@sf.net>
@ 2004-09-03 17:03 ` Adi Alurkar <adi@sf.net>
  2004-09-04 10:19   ` Re: Dump/Restore vs Vacuum Full Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Adi Alurkar @ 2004-09-03 17:03 UTC (permalink / raw)
  To: pgsql-admin

Any comments ?
knock knock!! is this thing ON?

On Sep 1, 2004, at 5:59 PM, Adi Alurkar wrote:

> Greetings,
>
> Are there any differences, advantages of running a dump/restore vs 
> running the following:1)REINDEX all the tables in all the databases, 
> 2)VACUUM FULL ANALYZE on all the databases
>
> Assuming the following
> 1) the system can be offline.
> 2) PG version 7.4.x
> 3) pg_autovacuum running as a daemon with 30 minutes sleep but have 
> had a few occasions where pg_autovacuum had to be killed and 
> restarted.
> 4) FSM settings are set > than required by VACUUM ANALYZE VERBOSE 
> "test".
>
> -Adi
>
>
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if 
> your
>      joining column's datatypes do not match
>
>
--
Adi Alurkar (DBA sf.NET) <adi@vasoftware.com>
1024D/79730470 A491 5724 74DE 956D 06CB  D844 6DF1 B972 7973 0470





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Dump/Restore vs Vacuum Full
  2004-09-02 00:59 Dump/Restore vs Vacuum Full Adi Alurkar <adi@sf.net>
  2004-09-03 17:03 ` Re: Dump/Restore vs Vacuum Full Adi Alurkar <adi@sf.net>
@ 2004-09-04 10:19   ` Gaetano Mendola <mendola@bigfoot.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Gaetano Mendola @ 2004-09-04 10:19 UTC (permalink / raw)
  To: Adi Alurkar <adi@sf.net>

Adi Alurkar wrote:
> Any comments ?
> knock knock!! is this thing ON?
> 
> On Sep 1, 2004, at 5:59 PM, Adi Alurkar wrote:
> 
>> Greetings,
>>
>> Are there any differences, advantages of running a dump/restore vs 
>> running the following:1)REINDEX all the tables in all the databases, 
>> 2)VACUUM FULL ANALYZE on all the databases
>>
>> Assuming the following
>> 1) the system can be offline.
>> 2) PG version 7.4.x
>> 3) pg_autovacuum running as a daemon with 30 minutes sleep but have 
>> had a few occasions where pg_autovacuum had to be killed and restarted.
>> 4) FSM settings are set > than required by VACUUM ANALYZE VERBOSE "test".

Go for a vacuum full and reindex of all tables. The advantages are that
the dump/restore is longer if your vacuum the database quite enough

BTW, with 7.4.x there is no needs to run vacuum full so much

Regards
Gaetano Mendola











^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2004-09-04 10:19 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-09-02 00:59 Dump/Restore vs Vacuum Full Adi Alurkar <adi@sf.net>
2004-09-03 17:03 ` Adi Alurkar <adi@sf.net>
2004-09-04 10:19   ` Gaetano Mendola <mendola@bigfoot.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox