View Full Version : Pgsql Performance


Pages : 1 2 3 4 5 6 7 [8] 9 10 11 12 13 14 15 16

  1. Selects query stats?
  2. Re: slow query using sub select
  3. slow query using sub select
  4. Query hanging/not finishing inconsistently
  5. Query performance
  6. Performs WAY better with enable_seqscan = off
  7. how to improve Performance
  8. Benchmarking Function
  9. utilizing multiple disks for i/o performance
  10. How can I make this query faster (resend)
  11. Re: why is bitmap index chosen for this query?
  12. why is bitmap index chosen for this query?
  13. Re: Performance/Maintenance test result collection
  14. Re: Benchmarck PostgreSQL 8.1.4 MySQL 5.0.20 and Oracle 10g2
  15. Benchmarck PostgreSQL 8.1.4 MySQL 5.0.20 and Oracle 10g2
  16. Performance/Maintenance test result collection
  17. SQL CPU time usage
  18. Want a serious muslim match?Join our club and start searching now!!!
  19. Performance incorporate with JReport
  20. Adding and filling new column on big table
  21. Pgsql (and mysql) benchmark on T2000/Solaris and some profiling
  22. IMMUTABLE?
  23. stable function optimizations, revisited
  24. Re: slow variable against int??
  25. Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)
  26. Wrong plan for subSELECT with GROUP BY
  27. Re: Nested Loops vs. Hash Joins or Merge Joins
  28. Same query - Slow in production
  29. Re: [GENERAL] Arguments Pro/Contra Software Raid
  30. Question about explain-command...
  31. Re: in memory views
  32. in memory views
  33. UNSUBSCRIBE
  34. Dynamically loaded C function performance
  35. slow variable against int??
  36. Postgres gets stuck
  37. Slow C Function
  38. Re: Memory and/or cache issues?
  39. PostgreSQL VACCUM killing CPU
  40. VACUUM killing my CPU
  41. Arguments Pro/Contra Software Raid
  42. Re: extremely slow when execute select/delete for certain tables
  43. Assistance with optimizing query - same SQL, different category_id = Seq Scan
  44. performance question (something to do w/ parameterized stmts?, wrongindex types?)
  45. Query runs 38 seconds for small database!
  46. extremely slow when execute select/delete for certain tables only...
  47. pg_dump index creation order
  48. Re: Memory and/or cache issues?
  49. Re: Memory and/or cache issues?
  50. Re: Memory and/or cache issues?
  51. Re: Memory and/or cache issues?
  52. Re: Memory and/or cache issues?
  53. Re: Memory and/or cache issues?
  54. Re: Memory and/or cache issues?
  55. Memory and/or cache issues?
  56. Re: Performance Issues on Opteron Dual Core
  57. Re: Postgres 7.4 and vacuum_cost_delay.
  58. Re: Performance Issues on Opteron Dual Core
  59. Re: Performance Issues on Opteron Dual Core
  60. Lot'sa joins - performance tip-up, please?
  61. Killing long-running queries
  62. Nested loop join and date range query
  63. Re: Postgres 7.4 and vacuum_cost_delay.
  64. Re: Why is plan (and performance) different on partitioned table?
  65. postgresql transaction id monitoring with nagios
  66. Why is plan (and performance) different on partitioned table?
  67. Re: Hardware: HP StorageWorks MSA 1500
  68. Postgres 7.4 and vacuum_cost_delay.
  69. Cluster vs. non-cluster query planning
  70. Re: Super-smack?
  71. Super-smack?
  72. Slow restoration question
  73. Performance Issues on Opteron Dual Core
  74. Re: hardare config question
  75. hardare config question
  76. Arrays and index scan
  77. query performance question
  78. Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
  79. CPU usage goes to 100%, query seems to ran forever
  80. Why so slow?
  81. Firebird 1.5.3 X Postgresql 8.1.3 (linux Firebird 1.5.3 X Postgresql 8.1.3 (linux and and windows)]
  82. Re: how unsafe (or worst scenarios) when setting fsync OFF for postgresql
  83. how unsafe (or worst scenarios) when setting fsync OFF for postgresql
  84. Running on an NFS Mounted Directory
  85. Re: WAL logging of SELECT ... INTO command
  86. Re: Large (8M) cache vs. dual-core CPUs
  87. Re: Large (8M) cache vs. dual-core CPUs
  88. Re: Large (8M) cache vs. dual-core CPUs
  89. Re: Firebird 1.5.3 X Postgresql 8.1.3 (linux and windows)
  90. Re: Large (8M) cache vs. dual-core CPUs
  91. slow deletes on pgsql 7.4
  92. Re: Large (8M) cache vs. dual-core CPUs
  93. Re: planner not using index for like operator
  94. Re: planner not using index for like operator
  95. Large (8M) cache vs. dual-core CPUs
  96. Slow queries salad ;)
  97. planner not using index for like operator
  98. PL/pgSQL Loop Vs. Batch Update
  99. Query on postgresql 7.4.2 not using index
  100. Re: serious problems with vacuuming databases
  101. Introducing a new linux readahead framework
  102. Slow deletes in 8.1 when FKs are involved
  103. ip address data type
  104. Re: Hardware: HP StorageWorks MSA 1500
  105. Index on function less well cached than "regular" index ?
  106. Slow deletes in 8.1 when FKs are involved
  107. GROUP BY Vs. Sub SELECT
  108. Easy question
  109. Re: WAL logging of SELECT ... INTO command
  110. Re: Hardware: HP StorageWorks MSA 1500
  111. Worsening performance with 7.4 on flash-based system
  112. security for row level but not based on Database user's login
  113. Little use of CPU ( < 5%)
  114. Better way to write aggregates?
  115. Introducing a new linux readahead framework
  116. Recovery will take 10 hours
  117. Hardware: HP StorageWorks MSA 1500
  118. Performance decrease
  119. IBM pSeries - overrated bucket of crud?
  120. Identical query on two machines, different plans....
  121. Quick Performance Poll
  122. Re: Perfrmance Problems (7.4.6)
  123. Re: Perfrmance Problems (7.4.6)
  124. Re: Inserts optimization?
  125. Planner doesn't chose Index - (slow select)
  126. Multicolumn order by
  127. Re: creating of temporary table takes very long
  128. Re: Problem with LIKE-Performance
  129. Problem with LIKE-Performance
  130. SELECT FOR UPDATE performance is bad
  131. Re: Inserts optimization?
  132. Re: Migration study, step 2: rewriting queries
  133. Re: creating of temporary table takes very long
  134. Re: creating of temporary table takes very long
  135. Re: creating of temporary table takes very long
  136. creating of temporary table takes very long
  137. slow cursor
  138. Migration study, step 2: rewriting queries
  139. merge>hash>loop
  140. pg_toast size
  141. Re: multi column query
  142. Re: Blocks read for index scans
  143. Blocks read for index scans
  144. Re: multi column query
  145. Re: Better index stategy for many fields with few values
  146. index is not used if I include a function that returns current timein my query
  147. Re: Better index stategy for many fields with few values
  148. Slow query - possible bug?
  149. index is not used if I include a function that returns current timein my query
  150. pg 7.4.x - pg_restore impossibly slow
  151. Inserts optimization?
  152. multi column query
  153. Re: Better index stategy for many fields with few values
  154. Re: Sequencial scan instead of using index
  155. Re: Sequencial scan instead of using index
  156. Re: Sequencial scan instead of using index
  157. FOREIGN KEYS vs PERFORMANCE
  158. Stored Procedure Performance
  159. Encouraging multi-table join order
  160. Better index stategy for many fields with few values
  161. Re:
  162. Dump restore performance 7.3 -> 8.1
  163. Restore performance?
  164. Takes too long to fetch the data from database
  165. slow "IN" clause
  166. serious problems with vacuuming databases
  167. Re:
  168. Re:
  169. pls reply ASAP
  170. OT: Data structure design question: How do they count so fast?
  171. pg 8.1.3, AIX, huge box, painfully slow.
  172. Loading the entire DB into RAM
  173. Same SQL, 104296ms of difference between 7.4.12 and 8.0.7
  174. CURSOR OR OFFSET/LIMIT
  175. Re: Intel C/C++ Compiler Tests (fwd)
  176. Re: Sun Fire T2000 and PostgreSQL 8.1.3
  177. Maintenance_work_mem influence on queries
  178. Query planner is using wrong index.
  179. Re: Sun Fire T2000 and PostgreSQL 8.1.3
  180. Re: Sun Fire T2000 and PostgreSQL 8.1.3
  181. Re: Sun Fire T2000 and PostgreSQL 8.1.3
  182. Re: Sun Fire T2000 and PostgreSQL 8.1.3
  183. Sun Fire T2000 and PostgreSQL 8.1.3
  184. Re: Query runs too long for indexed tables
  185. Re: Query runs too long for indexed tables
  186. Query runs too long for indexed tables
  187. vacuum full seems to hang on very small table
  188. pgmemcache
  189. freebsd/softupdates for data dir
  190. bad performance on Solaris 10
  191. The order of fields around the "=" in the WHERE conditions
  192. optimizing db for small table with tons of updates
  193. Measuring the execution time of functions within functions...
  194. Trigger vs Rule
  195. Re: [Solved] Slow performance on Windows .NET and OleDb
  196. un-'vacuum analyse'
  197. index not used again
  198. Automatic tuning of postgresql.conf parameters?
  199. Index scan startup time
  200. CREATE INDEX rather sluggish
  201. Query using SeqScan instead of IndexScan
  202. Re: Database possible corruption , unsolvable mystery
  203. Re: Database possible corruption , unsolvable mystery
  204. Database possible corruption , unsolvable mystery
  205. statistics buffer is full
  206. MVCC intro and benefits docs?
  207. Decide between Postgresql and Mysql (help of comunity)
  208. Slow performance on Windows .NET and OleDb
  209. Re: count(*) performance
  210. Re: count(*) performance
  211. Large Binary Objects Middleware
  212. simple join uses indexes, very slow
  213. Query parallelism
  214. count(*) performance
  215. Re: count(*) performance
  216. Re: [GENERAL] experiences needed - how does Itanium2/1.5GHz(4MB) compare to AMD and Intel CPUs as far as Postgresql is concerned
  217. Logging SQL queries to optimize them ?
  218. Performance problems with multiple layers of functions
  219. Problem with query, forget previous message
  220. Problem with query, server totally unresponsive
  221. Scaling up PostgreSQL in Multiple CPU / Dual Core Powered Servers
  222. Massive Inserts Strategies
  223. Intel C/C++ Compiler Tests
  224. Re: Migration study, step 1: bulk write performanceoptimization
  225. Re: Migration study, step 1: bulk write performanceoptimization
  226. motherboard recommendations
  227. Re: Sequence Scan vs. Index scan
  228. Sequence Scan vs. Index scan
  229. WAL logging of SELECT ... INTO command
  230. Postmaster using only 4-5% CPU
  231. Perfomance test figures
  232. Re: Best OS & Configuration for Dual Xeon w/4GB &
  233. Auto performance tuning?
  234. Query Feromance
  235. Migration study, step 1: bulk write performance optimization
  236. data doesnt get saved in the database / idle in transaction
  237. partial indexes and inference
  238. Re: Best OS & Configuration for Dual Xeon w/4GB &
  239. partitioning
  240. database model tshirt sizes
  241. n00b autovacuum question
  242. Best OS & Configuration for Dual Xeon w/4GB & Adaptec RAID 2200S
  243. planner with index scan cost way off actual cost, advices to tweak cost constants?
  244. Re: Indexes with descending date columns
  245. Help optimizing a slow index scan
  246. Re: 1 TB of memory
  247. Indexes with descending date columns
  248. 1 TB of memory
  249. PostgreSQL and Xeon MP
  250. Re: [HACKERS] BETWEEN optimizer problems with single-value range