[PERFORM] Improving performance on system catalog

2007-03-28 Thread Daniel Cristian Cruz
Hi all. I would like to speed up this query: EXPLAIN ANALYZE SELECT relid,schemaname,relname,seq_scan,seq_tup_read,idx_scan,idx_tup_fetch,n_tup_ins,n_tup_upd,n_tup_del FROM pg_stat_user_tables; QUERY PLAN

Re: [PERFORM] Improving performance on system catalog

2007-03-28 Thread chris smith
I would like to speed up this query: Total runtime: 13.844 ms Why bother? It's running in less than 14 milliseconds. -- Postgresql & php tutorials http://www.designmagick.com/ ---(end of broadcast)--- TIP 7: You can help support the Postgr

Re: [PERFORM] Improving performance on system catalog

2007-03-28 Thread Daniel Cristian Cruz
2007/3/28, chris smith <[EMAIL PROTECTED]>: > Total runtime: 13.844 ms Why bother? Because faster could be better in a very busy system. -- Daniel Cristian Cruz Analista de Sistemas

Re: [PERFORM] Improving performance on system catalog

2007-03-28 Thread Joshua D. Drake
Daniel Cristian Cruz wrote: Hi all. I would like to speed up this query: EXPLAIN ANALYZE SELECT relid,schemaname,relname,seq_scan,seq_tup_read,idx_scan,idx_tup_fetch,n_tup_ins,n_tup_upd,n_tup_del FROM pg_stat_user_tables; Although optimizing for 13ms is a little silly imo, you could prob

Re: [PERFORM] Improving performance on system catalog

2007-03-28 Thread Tom Lane
"Daniel Cristian Cruz" <[EMAIL PROTECTED]> writes: > 2007/3/28, chris smith <[EMAIL PROTECTED]>: >>> Total runtime: 13.844 ms >> >> Why bother? > Because faster could be better in a very busy system. If you are concerned about global performance improvement, quit worrying about this micro-detail

Re: [PERFORM] Improving performance on system catalog

2007-03-28 Thread Daniel Cristian Cruz
2007/3/28, Tom Lane <[EMAIL PROTECTED]>: "Daniel Cristian Cruz" <[EMAIL PROTECTED]> writes: > 2007/3/28, chris smith <[EMAIL PROTECTED]>: >>> Total runtime: 13.844 ms >> >> Why bother? > Because faster could be better in a very busy system. If you are concerned about global performance improve

[PERFORM] Shared buffers, db transactions commited, and write IO on Solaris

2007-03-28 Thread Erik Jones
Greetings, We've recently made a couple changes to our system that have resulted in a drastic increase in performance as well as some very confusing changes to the database statistics, specifically pg_stat_database.xact_commit. Here's the details: OS: Solaris10 x86 Server: Sunfire X4100,

[PERFORM] Planner doing seqscan before indexed join

2007-03-28 Thread Dan Harris
8.0.3 - Linux 2.6.18.. Freshly vacuumed and analyzed This database has been humming along fine for a while now, but I've got one of those sticky queries that is taking much too long to finish. After some digging, I've found that the planner is choosing to apply a necessary seq scan to the tabl