Adding new notes takes a ton of space (Vacuum database pgAdmin!!)
Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default Adding new notes takes a ton of space (Vacuum database pgAdmin!!)

    Hi,

    here's the problem. I have a big database. It takes about 64Gb of disk space. Now when I create a new definition and then run a task to create notes for it the DB becomes about 73Gb which is very much.

    If I reset notes and recreate them then it's ok. The space taken becomes reasonable.

    Is this a bug? If so then are you going to fix it? If not then how do I fix it?

  2. #2
    NoteCaddy sreticentv's Avatar
    Join Date
    Dec 2009
    Location
    No direction but to trust the final destination
    Posts
    6,481

    Default

    If you have a huge database (64 gb) then you should consider hiring a database administrator. Big databases require a large amount of work to maintain properly. Big companies have 64 gb databases and have teams of people to work on them
    NoteCaddy Manual | Coaching Packs | Blog
    NoteCaddy experts: a.k.aAlso, Catalyst_Kh, Derders, karstenkloss, scoobediah (NoteCaddy Edge)

  3. #3
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default

    Unfortunately I don't have such an option, but thanks for advice.

    Did I understand correctly that you're not considering such a behavior as a bug?

  4. #4
    Senior Member karstenkloss's Avatar
    Join Date
    Sep 2011
    Posts
    231

    Default

    In normal PostgreSQL operation, an UPDATE or DELETE of a row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (see Chapter 12): the row version must not be deleted while it is still potentially visible to other transactions. But eventually, an outdated or deleted row version is no longer of interest to any transaction. The space it occupies must be reclaimed for reuse by new rows, to avoid infinite growth of disk space requirements. This is done by running VACUUM.
    Hope this explains to you why this is not a bug.......

    PostgreSQL: Documentation: 8.1: Routine Database Maintenance Tasks

  5. #5
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default

    Hmm, I don't think it explains much because 10GB for one definition is quite a lot. I have 430 definitions that take 64gb and then just a single new one takes about ten.

    Also. From what is written in your post I make a conclusion that running vacuum should help. Is this a correct conclusion?

    I will run it right now. But I'm pretty sure that I tried it before and it didn't help.

  6. #6
    Senior Member karstenkloss's Avatar
    Join Date
    Sep 2011
    Posts
    231

    Default

    It's the explanation for the growth of your database.

    Make sure to run first "Vacuum (full)" and then "Reindex" as this order gives the best results.

  7. #7
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default

    Thank you.
    Here's what I'm running right now:

    QIP Shot -

    Is this the correct one?

  8. #8
    Senior Member karstenkloss's Avatar
    Join Date
    Sep 2011
    Posts
    231

    Default

    I always make it within PGAdminIII.....

  9. #9
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default

    Well, it didn't work. It freed up about 1gb of space...

  10. #10
    Senior Member
    Join Date
    Aug 2011
    Posts
    290

    Default

    Okay, I'll try PGAdmin

Similar Threads

  1. Replies: 13
    Last Post: 02-27-2010, 11:02 AM
  2. Replies: 7
    Last Post: 01-25-2010, 02:15 PM
  3. PGAdmin Password Error - Vacuum
    By ScottieB_08 in forum Manager General
    Replies: 1
    Last Post: 01-17-2010, 12:33 PM
  4. pgadmin iii vacuum
    By henrics in forum Manager General
    Replies: 2
    Last Post: 12-19-2008, 01:42 PM
  5. vacuum through pgadmin
    By JNuey in forum Manager General
    Replies: 1
    Last Post: 09-11-2008, 10:27 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •