View Full Version : Pgsql Performance


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

  1. Problem with 7.4.5 and webmin 1.8 in grant function
  2. bad performances using hashjoin
  3. Degradation of postgres 7.4.5 on FreeBSD/CygWin
  4. Effects of IDLE processes
  5. VACUUM ANALYZE slows down query
  6. PG proper configuation for a php forum
  7. Re: seq scan cache vs. index cache smackdown
  8. Re: seq scan cache vs. index cache smackdown
  9. Re: VACCUM FULL ANALYZE PROBLEM
  10. Re: seq scan cache vs. index cache smackdown
  11. disagreeing query planners
  12. Re: seq scan cache vs. index cache smackdown
  13. Re: VACCUM FULL ANALYZE PROBLEM
  14. Autocommit
  15. VACCUM FULL ANALYZE PROBLEM
  16. seq scan cache vs. index cache smackdown
  17. String matching
  18. Re: Autocommit
  19. estimated rows vs. actual rows
  20. Need 2,500 - 10,000 People
  21. How to interpret this explain analyse?
  22. Performance Tuning
  23. Re: Performance Tuning
  24. Re: How to interpret this explain analyse?
  25. Re: How to interpret this explain analyse?
  26. Re: Benchmark
  27. Re: How to interpret this explain analyse?
  28. Benchmark
  29. Re: How to interpret this explain analyse?
  30. Large time difference between explain analyze and normal run
  31. Re: Benchmark
  32. annotated PostgreSQL.conf now up
  33. Re: Performance Tuning
  34. Re: Performance Tuning
  35. Tell postgres which index to use?
  36. Re: Performance Tuning
  37. Re: Performance Tuning
  38. Re: Performance Tuning
  39. Re: Tell postgres which index to use?
  40. Re: How can I make use of both CPUs in a dual processor
  41. How can I make use of both CPUs in a dual processor machine
  42. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  43. Slow Restoration of a template1 Database (ALTER GROUP)
  44. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  45. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  46. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  47. Solaris 9 tuning
  48. Legal Money Using PayPal
  49. Re: Retry: Is this possible / slow performance?
  50. Re: Retry: Is this possible / slow performance?
  51. Retry: Is this possible / slow performance?
  52. Re: Retry: Is this possible / slow performance?
  53. Index not used with or condition
  54. Re: Index not used with or condition
  55. Re: Index not used with or condition
  56. Is this possible / slow performance?
  57. Are JOINs allowed with DELETE FROM
  58. Re: Are JOINs allowed with DELETE FROM
  59. Can the V7.3 EXPLAIN ANALYZE be trusted?
  60. Re: Are JOINs allowed with DELETE FROM
  61. Re: Can the V7.3 EXPLAIN ANALYZE be trusted?
  62. query produces 1 GB temp file
  63. Re: Planner really hates nested loops
  64. Re: High end server and storage for a PostgreSQL OLTP system
  65. Re: High end server and storage for a PostgreSQL OLTP system
  66. Tunning postgresql on linux (fedora core 3)
  67. GiST indexes and concurrency (tsearch2)
  68. Re: Bad query optimizer misestimation because of TOAST
  69. Re: Flattening a kind of 'dynamic' table
  70. Re: [postgis-users] Bad query optimizer misestimation because of
  71. Re: Tunning postgresql on linux (fedora core 3)
  72. Re: Tunning postgresql on linux (fedora core 3)
  73. Re: Planner really hates nested loops
  74. Planner really hates nested loops
  75. Re: GiST indexes and concurrency (tsearch2)
  76. Re: horizontal partition
  77. Re: horizontal partition
  78. Re: Bad query optimizer misestimation because of TOAST
  79. Re: High end server and storage for a PostgreSQL OLTP system
  80. Accessing insert values in triggers
  81. Performance of count(*) on large tables vs SQL Server
  82. horizontal partition
  83. Re: High end server and storage for a PostgreSQL OLTP system
  84. Re: Why the difference in query plan and performance pg
  85. Re: Postgres server getting slow!!
  86. Re: Automagic tuning
  87. Re: Very important choice
  88. High end server and storage for a PostgreSQL OLTP system
  89. Re: Performance of count(*) on large tables vs SQL Server
  90. Re: Automagic tuning
  91. Re: Index Slowing Insert >50x
  92. Re: High end server and storage for a PostgreSQL OLTP system
  93. Re: Performance of count(*) on large tables vs SQL Server
  94. Re: Automagic tuning
  95. Performance degredation at client site
  96. Re: Performance degredation at client site
  97. Re: Postgres server getting slow!!
  98. Re: Postgres server getting slow!!
  99. Re: Performance problem with semi-large tables
  100. Re: Performance problem with semi-large tables
  101. Re: Performance problem with semi-large tables
  102. Re: Performance problem with semi-large tables
  103. Re: Performance problem with semi-large tables
  104. Re: Flattening a kind of 'dynamic' table
  105. Postgres server getting slow!!
  106. Re: [SQL] OFFSET impact on Performance???
  107. Re: Flattening a kind of 'dynamic' table
  108. Flattening a kind of 'dynamic' table
  109. Re: [SQL] OFFSET impact on Performance???
  110. Re: PostgreSQL clustering VS MySQL clustering
  111. Bitmap indexes
  112. Re: Bitmap indexes
  113. Poor Performance on Postgres 8.0
  114. Triggers During COPY
  115. slow count()
  116. Re: Triggers During COPY
  117. Re: Flattening a kind of 'dynamic' table
  118. Re: [SQL] OFFSET impact on Performance???
  119. Re: Flattening a kind of 'dynamic' table
  120. Re: Ideal disk setup for Postgresql 7.4?
  121. Re: Flattening a kind of 'dynamic' table
  122. Optimizing Outer Joins
  123. Re: [SQL] OFFSET impact on Performance???
  124. SQL Performance Guidelines
  125. Re: SQL Performance Guidelines
  126. Upgrading from from 7.4.2 to 8.0
  127. Re: [SQL] OFFSET impact on Performance???
  128. Should the optimizer see this?
  129. Re: Possibly slow query
  130. Re: Upgrading from from 7.4.2 to 8.0
  131. Possibly slow query
  132. Re: Ideal disk setup for Postgresql 7.4?
  133. 200 times slower then MSSQL??
  134. Re: reltuples after vacuum and analyze
  135. PG versus FreeBSD, startup and connections problems
  136. Re: 200 times slower then MSSQL??
  137. Re: PgPool changes WAS: PostgreSQL clustering VS MySQL
  138. Postgres stopped running (shmget failed)
  139. PostgreSQL not utilising available memory
  140. Re: How to boost performance of ilike queries ?
  141. How to boost performance of ilike queries ?
  142. reltuples after vacuum and analyze
  143. Re: How to boost performance of ilike queries ?
  144. Re: poor performance of db?
  145. Re: reltuples after vacuum and analyze
  146. Re: [SQL] OFFSET impact on Performance???
  147. Re: How to boost performance of ilike queries ?
  148. poor performance of db?
  149. Re: PostgreSQL clustering VS MySQL clustering
  150. Re: PostgreSQL clustering VS MySQL clustering
  151. Re: PostgreSQL clustering VS MySQL clustering
  152. Re: PostgreSQL vs. Oracle vs. Microsoft
  153. Odd number of rows expected
  154. Re: PostgreSQL clustering VS MySQL clustering
  155. Profiling a function...
  156. Re: [SQL] OFFSET impact on Performance???
  157. inheritance performance
  158. Re: PostgreSQL clustering VS MySQL clustering
  159. DWH on Postgresql
  160. Re: PostgreSQL clustering VS MySQL clustering
  161. Re:
  162. Re: PostgreSQL clustering VS MySQL clustering
  163. Re: [SQL] OFFSET impact on Performance???
  164. Re: [SQL] OFFSET impact on Performance???
  165. Re:
  166. Re: [SQL] OFFSET impact on Performance???
  167. Re:
  168. PostgreSQL clustering VS MySQL clustering
  169. Re: PostgreSQL clustering VS MySQL clustering
  170. Re: PostgreSQL clustering VS MySQL clustering
  171. Which PARAMETER is most important for load query??
  172. Re: PostgreSQL clustering VS MySQL clustering
  173. Re: PostgreSQL clustering VS MySQL clustering
  174. Re: PostgreSQL clustering VS MySQL clustering
  175. Re: PostgreSQL clustering VS MySQL clustering
  176. Re: PostgreSQL clustering VS MySQL clustering
  177. Re: PostgreSQL clustering VS MySQL clustering
  178. Re: PostgreSQL clustering VS MySQL clustering
  179. OFFSET impact on Performance???
  180. Re: PostgreSQL clustering VS MySQL clustering
  181. Re: [SQL] OFFSET impact on Performance???
  182. column without pg_stats entry?!
  183. index scan of whole table, can't see why
  184. Re: index scan of whole table, can't see why
  185. Query performance and understanding explain analzye
  186. areca raid controller
  187. Re: Swapping on Solaris
  188. Disk configuration
  189. Re: Disk configuration
  190. Optimizing this count query
  191. Performance problem from migrating between versions!
  192. IN() Optimization issue in 8.0rc5
  193. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  194. Index on a function and SELECT DISTINCT
  195. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  196. Re: query optimization help
  197. query optimization help
  198. sum of all values
  199. Increasing RAM for more than 4 Gb. using postgresql
  200. Postgres Optimizer is not smart enough?
  201. Re: Increasing RAM for more than 4 Gb. using postgresql
  202. Re: Postgres Optimizer is not smart enough?
  203. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  204. Re: Postgres Optimizer is not smart enough?
  205. Re: Postgres Optimizer is not smart enough?
  206. Re: Increasing RAM for more than 4 Gb. using postgresql
  207. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  208. Re: Assimilation of these "versus" and hardware threads
  209. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  210. Re: [ADMIN] Assimilation of these "versus" and hardware threads
  211. Performance delay
  212. Re: Postgres Optimizer is not smart enough?
  213. Re: Postgres Optimizer is not smart enough?
  214. Re: PostgreSQL vs. Oracle vs. Microsoft
  215. Re: PostgreSQL vs. Oracle vs. Microsoft
  216. Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  217. Best filesystem for PostgreSQL Database Cluster under Linux
  218. which dual-CPU hardware/OS is fastest for PostgreSQL?
  219. Help with EXPLAIN ANALYZE runtimes
  220. Null integer columns
  221. Re: Null integer columns
  222. TEXT field and Postgresql Perfomance
  223. Re: TEXT field and Postgresql Perfomance
  224. Re: TEXT field and Postgresql Perfomance
  225. Does "HYPERTHREADING" do any harm if we use with RH9.0 and postgresql?
  226. Query across a date range
  227. Re: Query across a date range
  228. Re: Query across a date range
  229. Re: Low Performance for big hospital server ..
  230. Re: first postgrreSQL tunning
  231. PostgreSQL vs. Oracle vs. Microsoft
  232. first postgrreSQL tunning
  233. Problems with high traffic
  234. Benchmark two separate SELECTs versus one LEFT JOIN
  235. Re: query rewrite using materialized views
  236. Re: query rewrite using materialized views
  237. Re: Low Performance for big hospital server ..
  238. PostgreSQL's Statspack?
  239. Very Bad Performance.
  240. Bad Index Choices with user defined data type
  241. Re: sudden drop in statement turnaround latency -- yay!.
  242. query rewrite using materialized views
  243. Re: Low Performance for big hospital server ..
  244. Re: Low Performance for big hospital server ..
  245. Low Performance for big hospital server ..
  246. Optimization while compiling
  247. sudden drop in statement turnaround latency -- yay!.
  248. Wrong Stats and Poor Performance
  249. Re: Howto Increased performace ?
  250. Re: Howto Increased performace ?