Re: [PERFORM] : Create table taking time

2011-09-28 Thread Scott Marlowe
On Wed, Sep 28, 2011 at 11:06 AM, Venkat Balaji wrote: > Hello Everyone, > I am back with an issue (likely). > I am trying to create a table in our production database, and is taking 5 > seconds. > We have executed VACUUM FULL and yet to run ANALYZE. Can i expect the CREATE > TABLE to be faster af

Re: [PERFORM] : Create table taking time

2011-09-28 Thread Josh Berkus
> We have executed VACUUM FULL and yet to run ANALYZE. Can i expect the CREATE > TABLE to be faster after ANALYZE finishes ? The only way CREATE TABLE would be affected by VACUUM ANALYZE running is if you're saturating either your CPU or your disk 100%. Which you may be, on a low-end system. --

Re: [PERFORM] : Looking for PG Books

2011-09-28 Thread Josh Berkus
> Please let me know any source where i can get more books on PG, I am > especially looking for books on PG internals, architecture, Backup & > Recovery and HA. I'm afraid that you have to rely on the primary docs for now. The books which are out are a bit old (version 8.0 and 8.1) and do not co

[PERFORM] : Looking for PG Books

2011-09-28 Thread Venkat Balaji
Hello Everyone, I have been working on PostgreSQL for quite a while (2 yrs) now. I have got "PostgreSQL 9.0 High Performance" book today and quite excited to go through it. Please let me know any source where i can get more books on PG, I am especially looking for books on PG internals, architec

[PERFORM] : Create table taking time

2011-09-28 Thread Venkat Balaji
Hello Everyone, I am back with an issue (likely). I am trying to create a table in our production database, and is taking 5 seconds. We have executed VACUUM FULL and yet to run ANALYZE. Can i expect the CREATE TABLE to be faster after ANALYZE finishes ? Or is there anything serious ? Please sh

Re: [PERFORM] PostgreSQL-9.0 Monitoring System to improve performance

2011-09-28 Thread Tomas Vondra
On 28 Září 2011, 9:05, Greg Smith wrote: > Venkat Balaji wrote: >> >> 1. Big Full Table Scans >> 2. Table with high IOs (hot tables) >> 3. Highly used Indexes >> 4. Tables undergoing high DMLs with index scans 0 (with unused indexes) >> 5. Index usage for heap blk hits >> 6. Tracking Checkpoints >

Re: [PERFORM] PostgreSQL-9.0 Monitoring System to improve performance

2011-09-28 Thread Greg Smith
Venkat Balaji wrote: 1. Big Full Table Scans 2. Table with high IOs (hot tables) 3. Highly used Indexes 4. Tables undergoing high DMLs with index scans 0 (with unused indexes) 5. Index usage for heap blk hits 6. Tracking Checkpoints This is fairly easy to collect and analyze. You might take a