PDA

View Full Version : Pgsql Performance

Pages : 1 [2] 3 4 5 6 7 8 9 10 11 12 13 14 15 16
  1. M'I.5,Perse cution Haras sment t hrough the Radio
  2. M,I-5 Pers ecution Thr ee Years of MI5 P ersecution Fax es
  3. M`I 5`Pe rsecution . MI5 Wan t Me to Send Yo u the se Fa xes
  4. M I.5 Perse cution MI 5 Insi st tha t th ese Fax es mu st Continu e
  5. M I`5'Pers ecution , 22, 544 + 837 = 23,38 1
  6. Re: [GENERAL] Can't make backup
  7. Commit takes a long time.
  8. Linux/PostgreSQL scalability issue - problem with 8 cores
  9. M`I'5`Per secution ` Molestatio n durin g Tr avel
  10. M I`5,P ersecution M I5 a re A fraid to Adm it T heyre Behi nd the Persecution
  11. M`I'5`Persecu tion ` No Justic e f or the Vic tims of MI 5
  12. M-I'5.Persecuti on . MI 5 H ave Syst ematically Destroy ed My Life
  13. pg_dump performance
  14. With 4 disks should I go for RAID 5 or RAID 10
  15. Anyone running on RHEL Cluster?
  16. M I-5,Persecutio n Compari ng the MI 5 Persecuti on wit h German Final Soluti on
  17. M-I'5.Persecut ion . MI5 Wast e Taxp ayer M illions on Pointless Hate-Ca mpaign
  18. M-I 5`Persecutio n - Fo ur Years of MI 5 P ersecution Posts on Interne t Newsgrou ps
  19. M'I`5 Persecu tion , BBC N ewscasters L ie & Deny The yre Watchi ng Me
  20. More shared buffers causes lower performances
  21. Re: function body actors (was: viewing source code)
  22. Re: function body actors (was: viewing source code)
  23. Re: viewing source code
  24. performance index scan vs bitmap-seq scan.
  25. Minimizing dead tuples caused by update triggers
  26. Reinitialising stats once only without restarting
  27. Re: viewing source code
  28. Re: viewing source code
  29. Re: viewing source code
  30. Re: viewing source code
  31. Re: viewing source code
  32. Re: viewing source code
  33. Optimising a query
  34. Dual core Opterons beating quad core Xeons?
  35. Re: viewing source code
  36. Hi to ALL. I just join this group.
  37. Re: Evaluation of PG performance vs MSDE/MSSQL 2000 (not 2005)
  38. Re: viewing source code
  39. Re: update 600000 rows
  40. Re: SELECT * FROM table is too slow
  41. Re: update 600000 rows
  42. SELECT * FROM table is too slow
  43. explanation for seeks in VACUUM
  44. Re: viewing source code
  45. VACUUM FREEZE output more than double input
  46. update 600000 rows
  47. Putting files into fields in a table
  48. viewing source code
  49. Re: viewing source code
  50. Large Objects and Toast
  51. Heavy write activity on first vacuum of fresh TOAST data
  52. URI to kind of a benchmark
  53. Need help on parameters and their values to tune the postgresql database
  54. Limited performance on multi core server
  55. vacuumdb and autovacuum?
  56. Benchmarking PG
  57. Slow Query
  58. Measuring table and index bloat
  59. Combining two bitmap scans out performs a single regular index scan?
  60. Vacuum full since 15 hours
  61. Index on VARCHAR with text_pattern_ops inside PL/PGSQL procedure.
  62. Cost-Based Vacuum Delay tuning
  63. Trouble with LEFT JOIN using VIEWS.
  64. database tuning
  65. Re: Evaluation of PG performance vs MSDE/MSSQL 2000 (not2005)
  66. Re: Optimizer Not using the Right plan
  67. Evaluation of PG performance vs MSDE/MSSQL 2000 (not 2005)
  68. Bad query plans for queries on partitioned table
  69. Optimizer Not using the Right plan
  70. RAID arrays and performance
  71. PostgreSQL 8.2.5 slow performance on INSERT on Linux
  72. EXPLAIN ANALYZE time calculations
  73. Dealing with big tables
  74. Utilizing multiple cores for one query
  75. clear pg_stats
  76. Appending "LIMIT" to query drastically decreases performance
  77. Configuring a Large RAM PostgreSQL Server
  78. 7.4 Checkpoint Question
  79. Optimizer regression 8.2.1 -> 8.2.3 on TSEARCH2 queries with ORDER BY and LIMIT
  80. Windows XP selects are very slow
  81. GiST indexing tuples
  82. PostgreSQL performance on various distribution stock kernels
  83. 8.1 planner problem ?
  84. Query only slow on first run
  85. Base de Datos Transaccional
  86. doubt with pg_dump and high concurrent used databases
  87. TB-sized databases
  88. Re: tuning for TPC-C benchmark
  89. Performance problem with UNION ALL view and domains
  90. Problems with PostGreSQL and Windows 2003
  91. Increasing the database connections
  92. MI5 Persecution: Faxes Sent to Media1 (6307)
  93. MI5 Persecution: Faxes Sent to Media2 (8482)
  94. Postgres ignoring index when using left outer join.
  95. tuning for TPC-C benchmark
  96. MI5 Persecution: Victor Lewis-Smith (36757)
  97. MI5 Persecution: Balham Bus 8/7/99 (12832)
  98. MI5 Persecution: Clapham South 17/2/00 (15007)
  99. MI5 Persecution: Clapham Junction 6/5/00 (17182)
  100. MI5 Persecution: he's an idiot you know 3/11/00 (19357)
  101. MI5 Persecution: tinker tailor wanker thief 2/12/00 (21532)
  102. MI5 Persecution: Jon Holmes (4-5/Jan/2002) (23707)
  103. MI5 Persecution: Post Office 14/11/02 (25882)
  104. MI5 Persecution: Eclipse pub 20/12/02 (28057)
  105. MI5 Persecution: Barbican Library 6/2/2003 (30232)
  106. MI5 Persecution: Bernard Levin - The Times (32407)
  107. MI5 Persecution: Come back, Norma! (34582)
  108. MI5 Persecution: Introduction to Sent Faxes (1957)
  109. MI5 Persecution: Faxes Sent to Diplomatic/Legal (4132)
  110. =?windows-1256?Q?Performance_problem_(outer_join_+_view_+_no n-strict_func?==?windows-1256?Q?tions)=FE?=
  111. MI5 Persecution: BA984 LHR->TXL 13/6/98 (1957)
  112. MI5 Persecution: BHS Croydon 18/12/98 (4132)
  113. MI5 Persecution: Ravenscourt Park 20/3/99 (6307)
  114. MI5 Persecution: Battersea Library 29/3/99 (8482)
  115. MI5 Persecution: Royal Festival Hall 15/4/99 (10657)
  116. Clustered/covering indexes (or lack thereof :-)
  117. autovacuum: recommended?
  118. random_page_cost etc. per tablespace?
  119. ERROR: "invalid memory alloc request size" or "unexpected end ofdata" on large table
  120. difference between a unique constraint and a unique index ???
  121. MI5 Persecution: Neil Fox (Nov/1998) (1955)
  122. MI5 Persecution: Flying Eye (Mar/1999) (4129)
  123. MI5 Persecution: Johnny Boy (21/Aug/1998) (6303)
  124. MI5 Persecution: Johnny Boy (19/June/1999) (8477)
  125. MI5 Persecution: Brighton 24/9/98 (10651)
  126. MI5 Persecution: POSK 2/2/98 (12825)
  127. MI5 Persecution: Leicester Square 9/2/98 (14999)
  128. Can I Determine if AutoVacuum Does Anything?
  129. Curious about dead rows.
  130. work_mem and shared_buffers
  131. Help understanding stat numbers
  132. PostgreSQL vs MySQL, and FreeBSD
  133. Join performance
  134. Need to run CLUSTER to keep performance
  135. Subpar Execution Plan
  136. Re: partitioned table and ORDER BY indexed_field DESCLIMIT 1
  137. Estimation problem with a LIKE clause containing a /
  138. dell versus hp
  139. Re: Postgresql.conf Settings
  140. Migrating to 8.3 - checkpoints and background writer
  141. Database connections and stored procs (functions)
  142. index stat
  143. Which index methodology is better?-
  144. hp ciss on freebsd
  145. Training Recommendations
  146. Re: Hardware for PostgreSQL (RAID configurations)
  147. Union within View vs.Union of Views
  148. "MixedCase sensitive quoted" names
  149. hardware for PostgreSQL
  150. Unfortunate expansion of composite types in union
  151. How to avoid hashjoin and mergejoin
  152. select max(field) from table much faster with a group by clause?
  153. [Fwd: Re: Outer joins and Seq scans]
  154. Hardware for PostgreSQL
  155. tables with 300+ partitions
  156. Two fast queries get slow when combined
  157. Optimizing PostgreSQL for Windows
  158. High Availability and Load Balancing
  159. Improving Query
  160. Re: partitioned table and ORDER BY indexed_fieldDESCLIMIT 1
  161. Append Cost in query planners
  162. Outer joins and Seq scans
  163. Speed difference between select ... union select ... and select frompartitioned_table
  164. Re: partitioned table and ORDER BY indexed_field DESCLIMIT 1
  165. Suggestions on an update query
  166. Re: partitioned table and ORDER BY indexed_field DESCLIMIT 1
  167. PostgreSQL 8.3beta1 on Solaris testing case study
  168. 8.3beta1 testing on Solaris
  169. Bunching "transactions"
  170. Seq scan is used for "select count(*) from table" queries
  171. multiple apaches against single postgres database
  172. Finalizing commit taking very long
  173. Re: [SQL] two queryes in a single tablescan
  174. Re: need help with a query
  175. Memory Settings....
  176. Seqscan
  177. Re: need help with a query
  178. 12 hour table vacuums
  179. need help with a query
  180. Re: need help with a query
  181. how to improve the performance of creating index
  182. How to improve speed of 3 table join &group (HUGE tables)
  183. Re: two queryes in a single tablescan
  184. Incorrect estimates on columns
  185. Re: two queryes in a single tablescan
  186. Re: two queryes in a single tablescan
  187. Re: Vacuum goes worse
  188. using a stored proc that returns a result set in acomplex SQL stmt
  189. Select * query extremely slow only for some records on small,simple table - why?
  190. Autovacuum running out of memory
  191. Vacuum goes worse
  192. Exam Results
  193. Re: How to speed up min/max(id) in 50M rows table?
  194. How to speed up min/max(id) in 50M rows table?
  195. Huge amount of memory consumed during transaction
  196. building a performance test suite
  197. Performance problems with prepared statements
  198. Shared Buffer setting in postgresql.conf
  199. hashjoin chosen over 1000x faster plan
  200. Postgres running Very slowly
  201. SQL Monitoring
  202. Re: Apache2 PostgreSQL http authentication
  203. postgresql on NFS.. recommended? not recommended?
  204. A Must Read-MCSD!!!
  205. Apache2 PostgreSQL http authentication
  206. query plan worse after analyze
  207. Problems with + 1 million record table
  208. Slow TSearch2 performance for table with 1 million documents.
  209. quickly getting the top N rows
  210. Partitioning in postgres - basic question
  211. Tuning Help - What did I do wrong?
  212. can't shrink relation
  213. Query taking too long. Problem reading explain output.
  214. Re: Newbie question about degraded performance on delete statement. (SOLVED)
  215. Difference between Vacuum and Vacuum full
  216. Newbie question about degraded performance on delete statement.
  217. performance of like queries
  218. Partitioned table limitation
  219. Non-blocking vacuum full
  220. OOM Errors as a result of table inheritance and a bad plan(?)
  221. Postgres 7.4.2 hanging when vacuum full is run
  222. sequence query performance issues
  223. Tuning for warm standby
  224. Difference in query plan when using = or > in where clause
  225. Incorrect row estimates in plan?
  226. Attempting to disable count triggers on cleanup
  227. Poor performance with ON DELETE CASCADE
  228. Acceptable level of over-estimation?
  229. TEXT or LONGTEXT?
  230. Re: Low CPU Usage
  231. select count(*) performance (vacuum did not help)
  232. Re: Low CPU Usage
  233. SQL query required
  234. zero value in statistics collector's result
  235. Possible explanations for catastrophic performace deterioration?
  236. Re: Query planner unaware of possibly best plan
  237. Re: Low CPU Usage
  238. Re: Low CPU Usage
  239. Re: Low CPU Usage
  240. Re: Low CPU Usage
  241. Re: Low CPU Usage
  242. Re: Low CPU Usage
  243. Query planner unaware of possibly best plan
  244. Re: Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
  245. Searching for the cause of a bad plan
  246. Linux mis-reporting memory
  247. query io stats and finding a slow query
  248. Upgraded from 7.4 to 8.1.4 QUERIES NOW SLOW!!!
  249. Re: Low CPU Usage
  250. REPOST: Nested loops row estimates always too high