PDA

View Full Version : Pgsql Performance

Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 [15] 16
  1. more execution time
  2. What's better: Raid 0 or disk for seperate pg_xlog
  3. Multi-line requests in COPY ... FROM STDIN
  4. How to speed up tsearch2 indexing
  5. 64bit Opteron multi drive raid. Help with best config settings
  6. vacuum full, why multiple times ?
  7. Query Optimization
  8. Why would writes to pgsql_tmp bottleneck at 1mb/s?
  9. index scan on =, but not < ?
  10. pl/pgsql faster than raw SQL?
  11. bad plan
  12. Re: [pgsql-hackers-win32] Help with tuning this query (with
  13. performance problems
  14. Help with slow running query
  15. Re: [pgsql-hackers-win32] Help with tuning this query (with
  16. Re: [pgsql-hackers-win32] Help with tuning this query (with
  17. Re: [pgsql-hackers-win32] Help with tuning this query (with
  18. adding 'limit' leads to very slow query
  19. Re: [pgsql-hackers-win32] Help with tuning this query (with explain analyze finally)
  20. Re: [pgsql-hackers-win32] Help with tuning this query (with
  21. Re: Tuning, configuration for 7.3.5 on a Sun E4500
  22. Help trying to tune query that executes 40x slower than in SqlServer
  23. Re: [pgsql-hackers-win32] Help with tuning this query (with explain analyze finally)
  24. Re: [pgsql-hackers-win32] Help with tuning this query (with explain analyze finally)
  25. How to Partition?
  26. MAIN vs. PLAIN
  27. Select in FOR LOOP Performance
  28. Query's fast standalone - slow as a subquery.
  29. Re: name search query speed
  30. name search query speed
  31. Re: Help with tuning this query (with explain analyze finally)
  32. Performance tradeoff
  33. Help with tuning this query
  34. What is the postgres sql command for last_user_id ???
  35. Confusion about locales and 'like' indexes
  36. Re: multi billion row tables: possible or insane?
  37. multi billion row tables: possible or insane?
  38. Inheritence versus delete from
  39. wal_sync_methods
  40. PG block sizes
  41. Possible interesting extra information for explain analyze?
  42. Re: Peformance Tuning Opterons/ Hard Disk Layout
  43. IS NULL vs IS NOT NULL
  44. gah! sudden slowdown??
  45. Peformance Tuning Opterons/ Hard Disk Layout
  46. Re: Peformance Tuning Opterons/ Hard Disk Layout
  47. Re: Problem with 7.4.5 and webmin 1.8 in grant function
  48. Peformance Tuning Opterons/ Hard Disk Layout
  49. Re: PostgreSQL is extremely slow on Windows
  50. Re: PostgreSQL is extremely slow on Windows
  51. Re: Help me please !
  52. Re: Joins, Deletes and Indexes
  53. Re: PostgreSQL is extremely slow on Windows
  54. Re: Help me please !
  55. join vs. subquery
  56. subquery vs join on 7.4.5
  57. PostgreSQL is extremely slow on Windows
  58. Joins, Deletes and Indexes
  59. Inefficient Query Plans
  60. is pg_autovacuum so effective ?
  61. Re: PostgreSQL is extremely slow on Windows
  62. PostgreSQL is extremely slow on Windows
  63. Re: seq scan cache vs. index cache smackdown
  64. Re: seq scan cache vs. index cache smackdown
  65. Problem with 7.4.5 and webmin 1.8 in grant function
  66. bad performances using hashjoin
  67. Degradation of postgres 7.4.5 on FreeBSD/CygWin
  68. Effects of IDLE processes
  69. VACUUM ANALYZE slows down query
  70. PG proper configuation for a php forum
  71. Re: seq scan cache vs. index cache smackdown
  72. Re: seq scan cache vs. index cache smackdown
  73. Re: VACCUM FULL ANALYZE PROBLEM
  74. Re: seq scan cache vs. index cache smackdown
  75. disagreeing query planners
  76. Re: seq scan cache vs. index cache smackdown
  77. Re: VACCUM FULL ANALYZE PROBLEM
  78. Autocommit
  79. VACCUM FULL ANALYZE PROBLEM
  80. seq scan cache vs. index cache smackdown
  81. String matching
  82. Re: Autocommit
  83. estimated rows vs. actual rows
  84. Need 2,500 - 10,000 People
  85. How to interpret this explain analyse?
  86. Performance Tuning
  87. Re: Performance Tuning
  88. Re: How to interpret this explain analyse?
  89. Re: How to interpret this explain analyse?
  90. Re: Benchmark
  91. Re: How to interpret this explain analyse?
  92. Benchmark
  93. Re: How to interpret this explain analyse?
  94. Large time difference between explain analyze and normal run
  95. Re: Benchmark
  96. annotated PostgreSQL.conf now up
  97. Re: Performance Tuning
  98. Re: Performance Tuning
  99. Tell postgres which index to use?
  100. Re: Performance Tuning
  101. Re: Performance Tuning
  102. Re: Performance Tuning
  103. Re: Tell postgres which index to use?
  104. Re: How can I make use of both CPUs in a dual processor
  105. How can I make use of both CPUs in a dual processor machine
  106. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  107. Slow Restoration of a template1 Database (ALTER GROUP)
  108. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  109. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  110. Re: Slow Restoration of a template1 Database (ALTER GROUP)
  111. Solaris 9 tuning
  112. Legal Money Using PayPal
  113. Re: Retry: Is this possible / slow performance?
  114. Re: Retry: Is this possible / slow performance?
  115. Retry: Is this possible / slow performance?
  116. Re: Retry: Is this possible / slow performance?
  117. Index not used with or condition
  118. Re: Index not used with or condition
  119. Re: Index not used with or condition
  120. Is this possible / slow performance?
  121. Are JOINs allowed with DELETE FROM
  122. Re: Are JOINs allowed with DELETE FROM
  123. Can the V7.3 EXPLAIN ANALYZE be trusted?
  124. Re: Are JOINs allowed with DELETE FROM
  125. Re: Can the V7.3 EXPLAIN ANALYZE be trusted?
  126. query produces 1 GB temp file
  127. Re: Planner really hates nested loops
  128. Re: High end server and storage for a PostgreSQL OLTP system
  129. Re: High end server and storage for a PostgreSQL OLTP system
  130. Tunning postgresql on linux (fedora core 3)
  131. GiST indexes and concurrency (tsearch2)
  132. Re: Bad query optimizer misestimation because of TOAST
  133. Re: Flattening a kind of 'dynamic' table
  134. Re: [postgis-users] Bad query optimizer misestimation because of
  135. Re: Tunning postgresql on linux (fedora core 3)
  136. Re: Tunning postgresql on linux (fedora core 3)
  137. Re: Planner really hates nested loops
  138. Planner really hates nested loops
  139. Re: GiST indexes and concurrency (tsearch2)
  140. Re: horizontal partition
  141. Re: horizontal partition
  142. Re: Bad query optimizer misestimation because of TOAST
  143. Re: High end server and storage for a PostgreSQL OLTP system
  144. Accessing insert values in triggers
  145. Performance of count(*) on large tables vs SQL Server
  146. horizontal partition
  147. Re: High end server and storage for a PostgreSQL OLTP system
  148. Re: Why the difference in query plan and performance pg
  149. Re: Postgres server getting slow!!
  150. Re: Automagic tuning
  151. Re: Very important choice
  152. High end server and storage for a PostgreSQL OLTP system
  153. Re: Performance of count(*) on large tables vs SQL Server
  154. Re: Automagic tuning
  155. Re: Index Slowing Insert >50x
  156. Re: High end server and storage for a PostgreSQL OLTP system
  157. Re: Performance of count(*) on large tables vs SQL Server
  158. Re: Automagic tuning
  159. Performance degredation at client site
  160. Re: Performance degredation at client site
  161. Re: Postgres server getting slow!!
  162. Re: Postgres server getting slow!!
  163. Re: Performance problem with semi-large tables
  164. Re: Performance problem with semi-large tables
  165. Re: Performance problem with semi-large tables
  166. Re: Performance problem with semi-large tables
  167. Re: Performance problem with semi-large tables
  168. Re: Flattening a kind of 'dynamic' table
  169. Postgres server getting slow!!
  170. Re: [SQL] OFFSET impact on Performance???
  171. Re: Flattening a kind of 'dynamic' table
  172. Flattening a kind of 'dynamic' table
  173. Re: [SQL] OFFSET impact on Performance???
  174. Re: PostgreSQL clustering VS MySQL clustering
  175. Bitmap indexes
  176. Re: Bitmap indexes
  177. Poor Performance on Postgres 8.0
  178. Triggers During COPY
  179. slow count()
  180. Re: Triggers During COPY
  181. Re: Flattening a kind of 'dynamic' table
  182. Re: [SQL] OFFSET impact on Performance???
  183. Re: Flattening a kind of 'dynamic' table
  184. Re: Ideal disk setup for Postgresql 7.4?
  185. Re: Flattening a kind of 'dynamic' table
  186. Optimizing Outer Joins
  187. Re: [SQL] OFFSET impact on Performance???
  188. SQL Performance Guidelines
  189. Re: SQL Performance Guidelines
  190. Upgrading from from 7.4.2 to 8.0
  191. Re: [SQL] OFFSET impact on Performance???
  192. Should the optimizer see this?
  193. Re: Possibly slow query
  194. Re: Upgrading from from 7.4.2 to 8.0
  195. Possibly slow query
  196. Re: Ideal disk setup for Postgresql 7.4?
  197. 200 times slower then MSSQL??
  198. Re: reltuples after vacuum and analyze
  199. PG versus FreeBSD, startup and connections problems
  200. Re: 200 times slower then MSSQL??
  201. Re: PgPool changes WAS: PostgreSQL clustering VS MySQL
  202. Postgres stopped running (shmget failed)
  203. PostgreSQL not utilising available memory
  204. Re: How to boost performance of ilike queries ?
  205. How to boost performance of ilike queries ?
  206. reltuples after vacuum and analyze
  207. Re: How to boost performance of ilike queries ?
  208. Re: poor performance of db?
  209. Re: reltuples after vacuum and analyze
  210. Re: [SQL] OFFSET impact on Performance???
  211. Re: How to boost performance of ilike queries ?
  212. poor performance of db?
  213. Re: PostgreSQL clustering VS MySQL clustering
  214. Re: PostgreSQL clustering VS MySQL clustering
  215. Re: PostgreSQL clustering VS MySQL clustering
  216. Re: PostgreSQL vs. Oracle vs. Microsoft
  217. Odd number of rows expected
  218. Re: PostgreSQL clustering VS MySQL clustering
  219. Profiling a function...
  220. Re: [SQL] OFFSET impact on Performance???
  221. inheritance performance
  222. Re: PostgreSQL clustering VS MySQL clustering
  223. DWH on Postgresql
  224. Re: PostgreSQL clustering VS MySQL clustering
  225. Re:
  226. Re: PostgreSQL clustering VS MySQL clustering
  227. Re: [SQL] OFFSET impact on Performance???
  228. Re: [SQL] OFFSET impact on Performance???
  229. Re:
  230. Re: [SQL] OFFSET impact on Performance???
  231. Re:
  232. PostgreSQL clustering VS MySQL clustering
  233. Re: PostgreSQL clustering VS MySQL clustering
  234. Re: PostgreSQL clustering VS MySQL clustering
  235. Which PARAMETER is most important for load query??
  236. Re: PostgreSQL clustering VS MySQL clustering
  237. Re: PostgreSQL clustering VS MySQL clustering
  238. Re: PostgreSQL clustering VS MySQL clustering
  239. Re: PostgreSQL clustering VS MySQL clustering
  240. Re: PostgreSQL clustering VS MySQL clustering
  241. Re: PostgreSQL clustering VS MySQL clustering
  242. Re: PostgreSQL clustering VS MySQL clustering
  243. OFFSET impact on Performance???
  244. Re: PostgreSQL clustering VS MySQL clustering
  245. Re: [SQL] OFFSET impact on Performance???
  246. column without pg_stats entry?!
  247. index scan of whole table, can't see why
  248. Re: index scan of whole table, can't see why
  249. Query performance and understanding explain analzye
  250. areca raid controller