Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: current db growing very large

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Back to topic list

Re: current db growing very large

Reply

Author trnemani
Full name Todd Nemanich
Date 2003-09-10 10:36:57 PDT
Message Hunter, looking at the schema.py, I'm not seeing anything that would
generally get unbalanced quickly.

Burt, if you don't mind sending me some data, I can take a look and try
to figure out why this happened for you. I need two things. If you could
add verbose to that full vacuum (vacuum full verbose analyze) and send
me the output, that would help. Also, if you could send me the results
from the select relname,relfilenode,relpages from pg_class; then I can
look at that. I should be able to generate a pg maintinance script for
current given that. THX.

Todd Nemanich wrote:
> I will try to. In general, date/timestamp indecies are the worst for
> staying balanced.
>
> Hunter Matthews wrote:
>
>> Todd,
>> Any chance you could take a look at the code in head, and give me
>> your opinion on whether the newer code will keep the indexes balanced?
>>
>>
>> On Tue, 2003-09-09 at 20:25, Todd Nemanich wrote:
>>
>>> I have a pretty active postgres DB that I have to manage, and there
>>> are a couple things. First, for retriving blocks from tables you need
>>> to do a vacuum full analyze. Second, there's a good chance alot of
>>> your bloat is coming from unbalanced indecies. You should try this:
>>> select relname,relfilenode,relpages from pg_class;
>>> And see what's taking up lots of pages. You can compare with du -s -m
>>> in the data dir for your db. Reindex the tables that are causing you
>>> trouble.
>>> This should clear up your disk space, and help you fit into your
>>> pg shared memory space.
>>>
>>> Burt Holzman wrote:
>>>
>>>> Hunter Matthews wrote:
>>>>
>>>>
>>>>> Yes, there's some general database issues still existing in the HEAD
>>>>> tree. recent checkins, while breaking HEAD, should give an idea about
>>>>> how I intend to fix this.
>>>>>
>>>>> A later post suggested VACUUM ANALYSE on your db (my understanding is
>>>>> that should clear up a lot of the many duplicate deleted entries.)
>>>>>
>>>>> Does that make a difference on your DB?
>>>>
>>>>
>>>>
>>>> Thanks to Tom for the suggestion, but VACUUM ANALYZE did not seem to
>>>> reduce the size of the DB appreciably.
>>>>
>>>> - B
>>>>
>>>>
>>>>
>>>> --------------------​--------------------​--------------------​---------
>>>> To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
>>>> For additional commands, e-mail: users-help at current dot tigris dot org
>>>>
>>>
>>>
>>>
>>> --------------------​--------------------​--------------------​---------
>>> To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
>>> For additional commands, e-mail: users-help at current dot tigris dot org
>
>
>
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
> For additional commands, e-mail: users-help at current dot tigris dot org
>



--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
For additional commands, e-mail: users-help at current dot tigris dot org

« Previous message in topic | 5 of 5 | Next message in topic »

Messages

Show all messages in topic

Re: current db growing very large bholzm1 Burt Holzman 2003-09-09 09:25:16 PDT
     Re: current db growing very large trnemani Todd Nemanich 2003-09-09 17:25:14 PDT
         Re: current db growing very large hunterm Hunter Matthews 2003-09-10 08:12:56 PDT
             Re: current db growing very large trnemani Todd Nemanich 2003-09-10 08:31:35 PDT
                 Re: current db growing very large trnemani Todd Nemanich 2003-09-10 10:36:57 PDT
Messages per page: