- Selects query stats?
- Re: slow query using sub select
- slow query using sub select
- Query hanging/not finishing inconsistently
- Query performance
- Performs WAY better with enable_seqscan = off
- how to improve Performance
- Benchmarking Function
- utilizing multiple disks for i/o performance
- How can I make this query faster (resend)
- Re: why is bitmap index chosen for this query?
- why is bitmap index chosen for this query?
- Re: Performance/Maintenance test result collection
- Re: Benchmarck PostgreSQL 8.1.4 MySQL 5.0.20 and Oracle 10g2
- Benchmarck PostgreSQL 8.1.4 MySQL 5.0.20 and Oracle 10g2
- Performance/Maintenance test result collection
- SQL CPU time usage
- Want a serious muslim match?Join our club and start searching now!!!
- Performance incorporate with JReport
- Adding and filling new column on big table
- Pgsql (and mysql) benchmark on T2000/Solaris and some profiling
- IMMUTABLE?
- stable function optimizations, revisited
- Re: slow variable against int??
- Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)
- Wrong plan for subSELECT with GROUP BY
- Re: Nested Loops vs. Hash Joins or Merge Joins
- Same query - Slow in production
- Re: [GENERAL] Arguments Pro/Contra Software Raid
- Question about explain-command...
- Re: in memory views
- in memory views
- UNSUBSCRIBE
- Dynamically loaded C function performance
- slow variable against int??
- Postgres gets stuck
- Slow C Function
- Re: Memory and/or cache issues?
- PostgreSQL VACCUM killing CPU
- VACUUM killing my CPU
- Arguments Pro/Contra Software Raid
- Re: extremely slow when execute select/delete for certain tables
- Assistance with optimizing query - same SQL, different category_id = Seq Scan
- performance question (something to do w/ parameterized stmts?, wrongindex types?)
- Query runs 38 seconds for small database!
- extremely slow when execute select/delete for certain tables only...
- pg_dump index creation order
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Re: Memory and/or cache issues?
- Memory and/or cache issues?
- Re: Performance Issues on Opteron Dual Core
- Re: Postgres 7.4 and vacuum_cost_delay.
- Re: Performance Issues on Opteron Dual Core
- Re: Performance Issues on Opteron Dual Core
- Lot'sa joins - performance tip-up, please?
- Killing long-running queries
- Nested loop join and date range query
- Re: Postgres 7.4 and vacuum_cost_delay.
- Re: Why is plan (and performance) different on partitioned table?
- postgresql transaction id monitoring with nagios
- Why is plan (and performance) different on partitioned table?
- Re: Hardware: HP StorageWorks MSA 1500
- Postgres 7.4 and vacuum_cost_delay.
- Cluster vs. non-cluster query planning
- Re: Super-smack?
- Super-smack?
- Slow restoration question
- Performance Issues on Opteron Dual Core
- Re: hardare config question
- hardare config question
- Arrays and index scan
- query performance question
- Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- CPU usage goes to 100%, query seems to ran forever
- Why so slow?
- Firebird 1.5.3 X Postgresql 8.1.3 (linux Firebird 1.5.3 X Postgresql 8.1.3 (linux and and windows)]
- Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- how unsafe (or worst scenarios) when setting fsync OFF for postgresql
- Running on an NFS Mounted Directory
- Re: WAL logging of SELECT ... INTO command
- Re: Large (8M) cache vs. dual-core CPUs
- Re: Large (8M) cache vs. dual-core CPUs
- Re: Large (8M) cache vs. dual-core CPUs
- Re: Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)
- Re: Large (8M) cache vs. dual-core CPUs
- slow deletes on pgsql 7.4
- Re: Large (8M) cache vs. dual-core CPUs
- Re: planner not using index for like operator
- Re: planner not using index for like operator
- Large (8M) cache vs. dual-core CPUs
- Slow queries salad ;)
- planner not using index for like operator
- PL/pgSQL Loop Vs. Batch Update
- Query on postgresql 7.4.2 not using index
- Re: serious problems with vacuuming databases
- Introducing a new linux readahead framework
- Slow deletes in 8.1 when FKs are involved
- ip address data type
- Re: Hardware: HP StorageWorks MSA 1500
- Index on function less well cached than "regular" index ?
- Slow deletes in 8.1 when FKs are involved
- GROUP BY Vs. Sub SELECT
- Easy question
- Re: WAL logging of SELECT ... INTO command
- Re: Hardware: HP StorageWorks MSA 1500
- Worsening performance with 7.4 on flash-based system
- security for row level but not based on Database user's login
- Little use of CPU ( < 5%)
- Better way to write aggregates?
- Introducing a new linux readahead framework
- Recovery will take 10 hours
- Hardware: HP StorageWorks MSA 1500
- Performance decrease
- IBM pSeries - overrated bucket of crud?
- Identical query on two machines, different plans....
- Quick Performance Poll
- Re: Perfrmance Problems (7.4.6)
- Re: Perfrmance Problems (7.4.6)
- Re: Inserts optimization?
- Planner doesn't chose Index - (slow select)
- Multicolumn order by
- Re: creating of temporary table takes very long
- Re: Problem with LIKE-Performance
- Problem with LIKE-Performance
- SELECT FOR UPDATE performance is bad
- Re: Inserts optimization?
- Re: Migration study, step 2: rewriting queries
- Re: creating of temporary table takes very long
- Re: creating of temporary table takes very long
- Re: creating of temporary table takes very long
- creating of temporary table takes very long
- slow cursor
- Migration study, step 2: rewriting queries
- merge>hash>loop
- pg_toast size
- Re: multi column query
- Re: Blocks read for index scans
- Blocks read for index scans
- Re: multi column query
- Re: Better index stategy for many fields with few values
- index is not used if I include a function that returns current timein my query
- Re: Better index stategy for many fields with few values
- Slow query - possible bug?
- index is not used if I include a function that returns current timein my query
- pg 7.4.x - pg_restore impossibly slow
- Inserts optimization?
- multi column query
- Re: Better index stategy for many fields with few values
- Re: Sequencial scan instead of using index
- Re: Sequencial scan instead of using index
- Re: Sequencial scan instead of using index
- FOREIGN KEYS vs PERFORMANCE
- Stored Procedure Performance
- Encouraging multi-table join order
- Better index stategy for many fields with few values
- Re:
- Dump restore performance 7.3 -> 8.1
- Restore performance?
- Takes too long to fetch the data from database
- slow "IN" clause
- serious problems with vacuuming databases
- Re:
- Re:
- pls reply ASAP
- OT: Data structure design question: How do they count so fast?
- pg 8.1.3, AIX, huge box, painfully slow.
- Loading the entire DB into RAM
- Same SQL, 104296ms of difference between 7.4.12 and 8.0.7
- CURSOR OR OFFSET/LIMIT
- Re: Intel C/C++ Compiler Tests (fwd)
- Re: Sun Fire T2000 and PostgreSQL 8.1.3
- Maintenance_work_mem influence on queries
- Query planner is using wrong index.
- Re: Sun Fire T2000 and PostgreSQL 8.1.3
- Re: Sun Fire T2000 and PostgreSQL 8.1.3
- Re: Sun Fire T2000 and PostgreSQL 8.1.3
- Re: Sun Fire T2000 and PostgreSQL 8.1.3
- Sun Fire T2000 and PostgreSQL 8.1.3
- Re: Query runs too long for indexed tables
- Re: Query runs too long for indexed tables
- Query runs too long for indexed tables
- vacuum full seems to hang on very small table
- pgmemcache
- freebsd/softupdates for data dir
- bad performance on Solaris 10
- The order of fields around the "=" in the WHERE conditions
- optimizing db for small table with tons of updates
- Measuring the execution time of functions within functions...
- Trigger vs Rule
- Re: [Solved] Slow performance on Windows .NET and OleDb
- un-'vacuum analyse'
- index not used again
- Automatic tuning of postgresql.conf parameters?
- Index scan startup time
- CREATE INDEX rather sluggish
- Query using SeqScan instead of IndexScan
- Re: Database possible corruption , unsolvable mystery
- Re: Database possible corruption , unsolvable mystery
- Database possible corruption , unsolvable mystery
- statistics buffer is full
- MVCC intro and benefits docs?
- Decide between Postgresql and Mysql (help of comunity)
- Slow performance on Windows .NET and OleDb
- Re: count(*) performance
- Re: count(*) performance
- Large Binary Objects Middleware
- simple join uses indexes, very slow
- Query parallelism
- count(*) performance
- Re: count(*) performance
- Re: [GENERAL] experiences needed - how does Itanium2/1.5GHz(4MB) compare to AMD and Intel CPUs as far as Postgresql is concerned
- Logging SQL queries to optimize them ?
- Performance problems with multiple layers of functions
- Problem with query, forget previous message
- Problem with query, server totally unresponsive
- Scaling up PostgreSQL in Multiple CPU / Dual Core Powered Servers
- Massive Inserts Strategies
- Intel C/C++ Compiler Tests
- Re: Migration study, step 1: bulk write performanceoptimization
- Re: Migration study, step 1: bulk write performanceoptimization
- motherboard recommendations
- Re: Sequence Scan vs. Index scan
- Sequence Scan vs. Index scan
- WAL logging of SELECT ... INTO command
- Postmaster using only 4-5% CPU
- Perfomance test figures
- Re: Best OS & Configuration for Dual Xeon w/4GB &
- Auto performance tuning?
- Query Feromance
- Migration study, step 1: bulk write performance optimization
- data doesnt get saved in the database / idle in transaction
- partial indexes and inference
- Re: Best OS & Configuration for Dual Xeon w/4GB &
- partitioning
- database model tshirt sizes
- n00b autovacuum question
- Best OS & Configuration for Dual Xeon w/4GB & Adaptec RAID 2200S
- planner with index scan cost way off actual cost, advices to tweak cost constants?
- Re: Indexes with descending date columns
- Help optimizing a slow index scan
- Re: 1 TB of memory
- Indexes with descending date columns
- 1 TB of memory
- PostgreSQL and Xeon MP
- Re: [HACKERS] BETWEEN optimizer problems with single-value range