Re: [PERFORM] slow joins?

and on line_items ? What are the stats settings for these tables ? HTH, Greg WIlliamson -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] slow joins?

Joe -- From: Joe Van Dyk j...@tanga.com To: Greg Williamson gwilliamso...@yahoo.com Cc: pgsql-performance@postgresql.org pgsql-performance@postgresql.org Sent: Friday, April 5, 2013 7:56 PM Subject: Re: [PERFORM] slow joins? On Fri, Apr 5, 2013 at 6:54 PM

Re: [PERFORM] How to keep queries low latency as concurrency increases

queries a second to the readonly boxes, about the same to a beefier read / write master. This is a slightly old pgbouncer at that ... used is a fairly basic mode. Greg Williamson -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription

Re: [PERFORM] Inserts in 'big' table slowing down the database

that are bigger than 1 hour -- too many partitions doesn't help. Greg Williamson -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] Index Bloat Problem

Thanks for this description--we have index bloat problems on a massively active (but small) database.This may help shed light on our problems. Sorry for top-posting--challenged email reader. Greg W. From: Jeff Janes jeff.ja...@gmail.com To: Strahinja

Re: [PERFORM] slow query, different plans

Midge -- Sorry for top-quoting -- challenged mail. Perhaps a difference in the stats estimates -- default_statistics_target ? Can you show us a diff between the postgres config files for each instance ? Maybe something there ... Greg Williamson From: Midge

Re: [PERFORM] PostgreSQL 9.0.1 on Windows performance tunning help please

? The row estimates seem to be off wildly, although that may be a symptom of something else and not related, it is worth ruling out the easily tried. HTH, Greg Williamson -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http

Re: [PERFORM] Autovacuum Tuning advice

Joe wrote: I have a very busy system that takes about 9 million inserts per day and each record gets updated at least once after the insert (all for the one same table), there are other tables that get hit but not as severely. As suspected I am having a problem with table bloat. Any

Re: [PERFORM] Message queue table - strange performance drop with changing limit size.

? Are the timing results consistent over several runs ? It is possible that caching effects are entering into the time results. Greg Williamson - Original Message From: Jesper Krogh jes...@krogh.cc To: pgsql-performance@postgresql.org Sent: Fri, January 1, 2010 3:48:43 AM Subject: [PERFORM] Message

Re: [PERFORM] Postgres query completion status?

but there may be better ways of doing that depending on what version you are using and what you maintenance window looks like. HTH, Greg W. From: Thom Brown thombr...@gmail.com To: Richard Neill rn...@cam.ac.uk Cc: Greg Williamson gwilliamso...@yahoo.com; pgsql

Re: [PERFORM] Postgres query completion status?

of caching of the desired rows, either by PostgreSQL or by your operating system. The rollback wouldn't effect this -- the rows are already in memory and not on disk waiting to be grabbed -- much faster on all subsequent queries. HTH, Greg Williamson -- Sent via pgsql-performance mailing list

Re: [PERFORM] Slow query after upgrade to 8.4

Jared -- Forgive the top-posting -- a challenged reader. I see this in the 8.4 analyze: Merge Cond: (cli.clientid = dv118488y0.clientid) Join Filter: ((dv118488y0.variableid = v118488y0.variableid) AND (dv118488y0.cycleid = c1.cycleid) AND (dv118488y0.unitid =

Re: [PERFORM] Newbie question about degraded performance on delete statement.

the planner says. Put this in a transaction and roll it back if you want to leave the data unchanged, e.g. BEGIN; EXPLAIN ANALYZE DELETE FROM foo WHERE pk = 1234; -- or whatever values you'd be using ROLLBACK; HTH, Greg Williamson Senior DBA GlobeXplorer LLC, a DigitalGlobe company