Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 07 Jan 2008 10:53:11 -0500
Geoffrey <[EMAIL PROTECTED]> wrote:
So, I'm wondering if anyone can point me to more specific information
as to when, if ever, you should 'vacuum full?'
1. If you over run your fsm pages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 07 Jan 2008 10:53:11 -0500
Geoffrey <[EMAIL PROTECTED]> wrote:
> So, I'm wondering if anyone can point me to more specific information
> as to when, if ever, you should 'vacuum full?'
1. If you over run your fsm pages
* Except that vacuum f
Scott Marlowe wrote:
Note that routine vacuum FULL is not a good idea actually. vacuum
full is something you run when things have gone wrong (i.e. not enough
regular vacuuming) and it is usually best followed by reindexing all
your indexes.
It's far better to keep track of bloat and run vacuum
> "Scott" == Scott Marlowe <[EMAIL PROTECTED]> writes:
Scott> Note that routine vacuum FULL is not a good idea actually.
Scott> vacuum full is something you run when things have gone wrong
Scott> (i.e. not enough regular vacuuming) and it is usually best
Scott> followed by reindexing all your
> "Joshua" == Joshua D Drake <[EMAIL PROTECTED]> writes:
Joshua> Autovacuum by default won't do enough work for many production
Joshua> databases. You still have to configure it.
OK. Thanks. Good to know.
-JimC
--
James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6
--
On Jan 4, 2008 9:35 AM, James Cloos <[EMAIL PROTECTED]> wrote:
> > "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> >> Why was the db using that extra five plus gigs?
>
> Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
>
> Sorry, I forgot to mention: autovacuum was enabled and
James Cloos wrote:
"Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Why was the db using that extra five plus gigs?
Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
Sorry, I forgot to mention: autovacuum was enabled and I also ran
this script every night via cron:
#!/bin/bash
F
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>> Why was the db using that extra five plus gigs?
Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
Sorry, I forgot to mention: autovacuum was enabled and I also ran
this script every night via cron:
#!/bin/bash
FULL=''
test $(d
James Cloos <[EMAIL PROTECTED]> writes:
> Right after the restore the db took up less than ten percent as much
> space as the backup. (For the backup I stopped pg and used rsync on
> the /var/lib/postgresql/data directory.)
> Why was the db using that extra five plus gigs?
Smells like a hadn't-b
Today I did a backup, dump, drop, create and restore on a db which
seemed to be taking up too much disk space after a vacuum full.
The db was using about six gigs (as backed up) and now uses about two
thirds of a gig after the restore (plus many inserts and a few deletes).
Right after the restore
10 matches
Mail list logo
