PDA

View Full Version : Pgsql Performance

Pages : 1 2 [3] 4 5 6 7 8 9 10 11 12 13 14 15 16
  1. Speed difference between select ... union select ... and select frompartitioned_table
  2. Re: partitioned table and ORDER BY indexed_field DESCLIMIT 1
  3. Suggestions on an update query
  4. Re: partitioned table and ORDER BY indexed_field DESCLIMIT 1
  5. PostgreSQL 8.3beta1 on Solaris testing case study
  6. 8.3beta1 testing on Solaris
  7. Bunching "transactions"
  8. Seq scan is used for "select count(*) from table" queries
  9. multiple apaches against single postgres database
  10. Finalizing commit taking very long
  11. Re: [SQL] two queryes in a single tablescan
  12. Re: need help with a query
  13. Memory Settings....
  14. Seqscan
  15. Re: need help with a query
  16. 12 hour table vacuums
  17. need help with a query
  18. Re: need help with a query
  19. how to improve the performance of creating index
  20. How to improve speed of 3 table join &group (HUGE tables)
  21. Re: two queryes in a single tablescan
  22. Incorrect estimates on columns
  23. Re: two queryes in a single tablescan
  24. Re: two queryes in a single tablescan
  25. Re: Vacuum goes worse
  26. using a stored proc that returns a result set in acomplex SQL stmt
  27. Select * query extremely slow only for some records on small,simple table - why?
  28. Autovacuum running out of memory
  29. Vacuum goes worse
  30. Exam Results
  31. Re: How to speed up min/max(id) in 50M rows table?
  32. How to speed up min/max(id) in 50M rows table?
  33. Huge amount of memory consumed during transaction
  34. building a performance test suite
  35. Performance problems with prepared statements
  36. Shared Buffer setting in postgresql.conf
  37. hashjoin chosen over 1000x faster plan
  38. Postgres running Very slowly
  39. SQL Monitoring
  40. Re: Apache2 PostgreSQL http authentication
  41. postgresql on NFS.. recommended? not recommended?
  42. A Must Read-MCSD!!!
  43. Apache2 PostgreSQL http authentication
  44. query plan worse after analyze
  45. Problems with + 1 million record table
  46. Slow TSearch2 performance for table with 1 million documents.
  47. quickly getting the top N rows
  48. Partitioning in postgres - basic question
  49. Tuning Help - What did I do wrong?
  50. can't shrink relation
  51. Query taking too long. Problem reading explain output.
  52. Re: Newbie question about degraded performance on delete statement. (SOLVED)
  53. Difference between Vacuum and Vacuum full
  54. Newbie question about degraded performance on delete statement.
  55. performance of like queries
  56. Partitioned table limitation
  57. Non-blocking vacuum full
  58. OOM Errors as a result of table inheritance and a bad plan(?)
  59. Postgres 7.4.2 hanging when vacuum full is run
  60. sequence query performance issues
  61. Tuning for warm standby
  62. Difference in query plan when using = or > in where clause
  63. Incorrect row estimates in plan?
  64. Attempting to disable count triggers on cleanup
  65. Poor performance with ON DELETE CASCADE
  66. Acceptable level of over-estimation?
  67. TEXT or LONGTEXT?
  68. Re: Low CPU Usage
  69. select count(*) performance (vacuum did not help)
  70. Re: Low CPU Usage
  71. SQL query required
  72. zero value in statistics collector's result
  73. Possible explanations for catastrophic performace deterioration?
  74. Re: Query planner unaware of possibly best plan
  75. Re: Low CPU Usage
  76. Re: Low CPU Usage
  77. Re: Low CPU Usage
  78. Re: Low CPU Usage
  79. Re: Low CPU Usage
  80. Re: Low CPU Usage
  81. Query planner unaware of possibly best plan
  82. Re: Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
  83. Searching for the cause of a bad plan
  84. Linux mis-reporting memory
  85. query io stats and finding a slow query
  86. Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
  87. Re: Low CPU Usage
  88. REPOST: Nested loops row estimates always too high
  89. REPOST: Performance improves only after repeated VACUUM/ANALYZE
  90. Re: Low CPU Usage
  91. Re: Tablespaces and NFS
  92. Re: Tablespaces and NFS
  93. Query works when kludged, but would prefer "best practice" solution
  94. DELETE queries slow down
  95. update command question?
  96. Watch Satellite TV On Your PC
  97. Regarding COPY command from Postgres 8.2.0
  98. Index files
  99. Long Running Commits - Not Checkpoints
  100. Clustered tables improves perfs ?
  101. Index usage when bitwise operator is used
  102. db performance/design question
  103. pg_dump blocking create database?
  104. efficient pattern queries (using LIKE, ~)
  105. 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
  106. More Vacuum questions...
  107. Barcelona vs Tigerton
  108. [Again] Postgres performance problem
  109. What to vacuum after deleting lots of tables
  110. random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
  111. Re: DRBD and Postgres: how to improve the perfomance?
  112. DRBD and Postgres: how to improve the perfomance?
  113. postgres memory management issues?
  114. How planner decides left-anchored LIKE can use index
  115. Reasonable amount of indices
  116. postgres memory management issues?
  117. Re: Hardware spec]
  118. Re: [ADMIN] ADO -PostgreSQL OLE DB Provider
  119. SAN vs Internal Disks
  120. Hardware spec
  121. GIST performance (PostGIS): the_geom vs. Envelope(the_geom)
  122. utilising multi-cpu/core machines?
  123. Re : optimize query with a maximum(date) extraction
  124. optimize query with a maximum(date) extraction
  125. Performance on 8CPU's and 32GB of RAM
  126. join tables vs. denormalization by trigger
  127. About autovacuum
  128. Vacum Analyze problem
  129. Re: [GENERAL] Performance issue with nested loop
  130. Slow Query
  131. schemas to limit data access
  132. schemas to limit data access
  133. 8.2 Autovacuum BUG ?
  134. Transaction Log
  135. Transaction Log
  136. LIKE query verses =
  137. Performance issue with nested loop
  138. Performance problem with table containing a lot of text (blog)
  139. Re: 8.2 Query 10 times slower than 8.1 (view-heavy)
  140. 8.2 Query 10 times slower than 8.1 (view-heavy)
  141. 8.2.4 Chooses Bad Query Plan
  142. Bitmap Heap Scan before using index
  143. Performance issue
  144. Performance across multiple schemas
  145. index & Bitmap Heap Scan
  146. server performance issues - suggestions for tuning
  147. Performance issue
  148. Postgres performance problem
  149. Shared memory usage
  150. MI5 Persecution: Neil Fox (March/1998) (5999)
  151. MI5 Persecution: Capital Radio (11/April/1997) (4776)
  152. MI5 Persecution: GLR: David Hepworth (9/May/1997) (3553)
  153. MI5 Persecution: GLR: David Hepworth (21/Feb/1997) (2330)
  154. MI5 Persecution: Life is so hard (1107)
  155. MI5 Persecution: BBC1 TV News - 18/Dec/2002 (8445)
  156. MI5 Persecution: Channel Four TV News - 10/April/2002 (7222)
  157. MI5 Persecution: BBC-TV See You, See Me - 7/Dec/2001 (5999)
  158. MI5 Persecution: C4 SnowMail - January/2001 (4776)
  159. MI5 Persecution: England expects every man to do his duty (3553)
  160. MI5 Persecution: Nicholas Witchell - 10/April/1999 (2330)
  161. MI5 Persecution: Chris Tarrant - 10/March/1999 (1107)
  162. Partioning tsearch2 a table into chunks and accessing via views
  163. significant vacuum issues - looking for suggestions
  164. partitioned table and ORDER BY indexed_field DESC LIMIT 1
  165. deadlock_timeout parameter in Postgresql.cof
  166. deadlock_timeout parameter in Postgresql.cof
  167. long-running query - needs tuning
  168. Installing PostgreSQL
  169. asynchronous commit feature
  170. Re: Long running transaction in pg_activity_log
  171. Long running transaction in pg_activity_log
  172. Fast tsearch2, trigram matching on short phrases
  173. io storm on checkpoints, postgresql 8.2.4, linux
  174. Poor Performance after Upgrade
  175. Optimising "in" queries
  176. Re: Autovacuum is running forever
  177. Autovacuum is running forever
  178. MI5 Persecution: Channel Four TV News - 12/Feb/1999 (5999)
  179. MI5 Persecution: Dimbleby / John Major, April 1997 (4776)
  180. MI5 Persecution: Ken Clarke (2), April 1997 (3553)
  181. MI5 Persecution: Ken Clarke (1), April 1997 (2330)
  182. MI5 Persecution: Overview (1107)
  183. MI5 Persecution: David Hepworth (2) 16/5/97 (18229)
  184. MI5 Persecution: Victor Lewis-Smith 9/5/97 (17006)
  185. MI5 Persecution: Continuing Silence 9/5/97 (15783)
  186. Re: Terminology Question
  187. MI5 Persecution: Peak Practice 26/4/97 (14560)
  188. MI5 Persecution: I am being ignored 17/4/97 (13337)
  189. MI5 Persecution: Striking out action 10/3/97 (12114)
  190. MI5 Persecution: David Hepworth (1) 26/2/97 (10891)
  191. MI5 Persecution: No Justice 20/11/96 (9668)
  192. MI5 Persecution: WTGROMT 18/11/96 (8445)
  193. MI5 Persecution: Excellent web page 19/10/96 (7222)
  194. MI5 Persecution: Usual targets of such abuse 10/10/96 (5999)
  195. MI5 Persecution: Just too crazy 30/9/96 (4776)
  196. MI5 Persecution: Latest technology 31/7/96 (3553)
  197. MI5 Persecution: BBC+ITN=MI5 23/7/96 (2330)
  198. MI5 Persecution: Silly-billy 6/7/96 (1107)
  199. MI5 Persecution: Silly-billy 6/7/96 (5999)
  200. MI5 Persecution: Old_500 5/7/96 (4776)
  201. MI5 Persecution: alt.fan.mike-corley 6/6/96 (3553)
  202. MI5 Persecution: Bernard Levin 1/6/96 (2330)
  203. MI5 Persecution: Fitted up 26/4/96 (1107)
  204. Re: [pgsql-jobs] Looking for database hosting
  205. Re: [pgsql-jobs] Looking for database hosting
  206. MI5 Persecution: Fitted up 26/4/96 (1107)
  207. schema design question
  208. Re: Help optimize view
  209. Re: Help optimize view
  210. Re: Fwd: Table Partitioning
  211. Performance Solaris vs Linux
  212. Raid Configurations
  213. Stable function optimisation
  214. Bad planner decision - bitmap scan instead of index
  215. Integrated perc 5/i
  216. Indexscan is only used if we use "limit n"
  217. RAID 10 or RAID 10 + RAID 1
  218. Stable function optimisation
  219. Proposal: Pluggable Optimizer Interface
  220. Re: Performance on writable views
  221. Bitmap Index Scan optimization opportunity
  222. Re: Help optimize view
  223. Performance of CREATE INDEX
  224. Dell Hardware Recommendations
  225. mid 2007 "best bang for the buck" hardware opinions
  226. How to ENABLE SQL capturing???
  227. select count(*) performance
  228. Update table performance
  229. Planner making wrong decisions 8.2.4. Insane cost calculations.
  230. Extreme slow select query 8.2.4
  231. Default Performance between 8.0 and 8.1
  232. Postgres optimizer
  233. Performance problems with large telemetric datasets on 7.4.2
  234. Why are distinct and group by choosing different plans?
  235. cpu throttling
  236. Semantics of PostgreSQL Server Log Stats
  237. Using EXECUTE in a function
  238. Seq scan on join table despite index and high statistics
  239. one left join screws up the query
  240. Query optimization....
  241. Re: Postgres configuration for 64 CPUs, 128 GB RAM...
  242. Questions on Tags table schema
  243. Re: Slow query with backwards index scan
  244. select on 1milion register = 6s
  245. Re: Slow query with backwards index scan
  246. Vacuum looping?
  247. Slow query with backwards index scan
  248. Re: update, truncate and vacuum
  249. update, truncate and vacuum
  250. disk filling up