PDA

View Full Version : Pgsql Performance

Pages : 1 2 3 4 [5] 6 7 8 9 10 11 12 13 14 15 16
  1. Re: [HACKERS] EXISTS optimization
  2. Optimization pg 8.14 and postgresql.conf
  3. Strange left outer join performance issue
  4. Re: Strange left outer join performance issue
  5. Re: Sunfire X4500 recommendations
  6. linux - server configuration for small database
  7. Sunfire X4500 recommendations
  8. Re: Performance of count(*)
  9. Lower Random Access Time vs RAID 0 / 1
  10. Potential memory usage issue
  11. Re: Potential memory usage issue
  12. Parallel Vacuum
  13. Performance of count(*)
  14. Re: Lower Random Access Time vs RAID 0 / 1
  15. Re: Performance of count(*)
  16. Re: Performance of count(*)
  17. Re: Performance of count(*)
  18. Re: Performance of count(*)
  19. Re: Parallel Vacuum
  20. Determining server load from client
  21. Horrible trigger performance after upgrade 8.0.12 -> 8.2.3
  22. Re: how small to split a table?
  23. Vacuum full is slow
  24. cache - postgres
  25. Performance Tuning and Disk Cache
  26. text equality worse than pattern matching (v8.1.8)
  27. function call vs staright query
  28. unsubscribe
  29. Re: Postgres batch write very slow - what to do
  30. Dispatch-Merge pattern
  31. TPC-H Benchmark - hardware
  32. unsubscribe
  33. Determine dead tuples size
  34. Exam:070-229-An Excellent Resource
  35. test ...please ignore
  36. Autocommit in libpq
  37. Postgres batch write very slow - what to do
  38. Execution plan changed after upgrade from 7.3.9 to 8.2.3
  39. PostgreSQL in virtual machine
  40. Deceiding which index to use
  41. function performance vs in-line sql
  42. configuring new server / many slow disks?
  43. When the Record Got Updated.
  44. compact flash disks?
  45. problem with wrong query planning and ineffective statistics
  46. Any advantage to integer vs stored date w. timestamp
  47. Automated test-suite for Postgres
  48. Re:
  49. help
  50. query slows down after vacuum analyze
  51. Re: Having performance problems with TSearch2
  52. strange performance regression between 7.4 and 8.1
  53. Turning off Autovacuum
  54. Estimate the size of the SQL file generated by pg_dump utility
  55. PostgreSQL 8.2.3 VACUUM Timings/Performance
  56. Hibernate left join
  57. Array indexes, GIN?
  58. Improving query performance
  59. strange performance regression between 7.4 and 8.1
  60. Identical Queries
  61. Performance Query
  62. increasing database connections
  63. Upgraded to 8.2.3 --- still having performance issues
  64. performances with Pentium D
  65. Re: Opinions on Raid
  66. [kris@obsecurity.org: Anyone interested in improving postgresql scaling?]
  67. [kris@obsecurity.org: Progress on scaling of FreeBSD on 8 CPU systems]
  68. Insert performance
  69. Opinions on Raid
  70. low memory usage reported by 'top' indicates poor tuning?
  71. Writting a "search engine" for a pgsql DB
  72. Vacuumdb - Max_FSM_Pages Problem.
  73. Server Startup Error
  74. Query Planner
  75. invalid page header in block 428 of relation "pg_attribute"
  76. which Xeon processors don't have the context switching problem
  77. long checkpoint_timeout
  78. Re: Very slow bytea data extraction
  79. Re: Very slow bytea data extraction
  80. Recommended Initial Settings
  81. R: Very slow bytea data extraction
  82. Very slow bytea data extraction
  83. Vacuum full very slow due to nonremovable dead rows...What makes the dead rows non-removable?
  84. slow update on 1M rows (worse with indexes)
  85. Disable result buffering to frontend clients
  86. General advice on user functions
  87. Auto-Vacuum in 8.1 was ineffective for me. 8.2 may work better?
  88. How to avoid vacuuming a huge logging table
  89. Postgres performance Linux vs FreeBSD
  90. SELECT performance problem
  91. slow subselects
  92. Query Optimization
  93. How to debug performance problems
  94. Fwd: Not Picking Index
  95. Not Picking Index
  96. strange issue for certain queries
  97. Slow query with 'or' clause
  98. Problem with joining queries.
  99. Re: An unwanted seqscan
  100. Re: Proximity query with GIST and row estimation
  101. Re: Proximity query with GIST and row estimation
  102. Benchmarking PGSQL?
  103. An unwanted seqscan
  104. quad or dual core Intel CPUs
  105. JOIN to a VIEW makes a real slow query
  106. CPU Usage
  107. Question about Bitmap Heap Scan/BitmapAnd
  108. many instances or many databases or many users?
  109. Re: limit + order by is slow if no rows in result set
  110. limit + order by is slow if no rows in result set
  111. pg on 64 bit windows
  112. Is there an equivalent for Oracle's user_tables.num_rows
  113. Can anyone make this code tighter? Too slow, Please help!
  114. cube operations slower than geo_distance() on production server
  115. Recreate big table
  116. Disk saturation
  117. Re: stats collector process high CPU utilization
  118. Speed up this query
  119. Help Needed
  120. Re: How long should it take to insert 200,000records?
  121. Re: explain analyze output for review (was:optimizing a geo_distance()...)
  122. Re: explain analyze output for review (was:optimizing a geo_distance()...)
  123. index scan through a subquery
  124. How long should it take to insert 200,000 records?
  125. optimizing a geo_distance() proximity query
  126. OT: Mac OS X disk buffer cache
  127. Re: trouble with a join on OS X
  128. trouble with a join on OS X
  129. drive configuration for a new server
  130. Subselect query enhancement
  131. Using statement_timeout as a performance tool?
  132. test
  133. Slow update
  134. Re: Very slow queries
  135. Very slow queries
  136. Re: Querying distinct values from a large table
  137. Querying distinct values from a large table
  138. Partitioning
  139. int4 vs varchar to store ip addr
  140. [OT] Very strange postgresql behaviour
  141. work-mem how do I identify the proper size
  142. work-mem
  143. IN operator causes sequential scan (vs. multiple OR expressions)
  144. Seqscan/Indexscan still a known issue?
  145. Tuning
  146. Auto Vacuum Problem
  147. how to plan for vacuum?
  148. Bad Row Count Estimate on View with 8.2
  149. Postgres processes have a burst of CPU usage
  150. extract(field from timestamp) vs date dimension
  151. slow result
  152. slow result
  153. PostgreSQL optimization expert wanted
  154. Autoanalyze settings with zero scale factor
  155. Vacuum v/s Autovacuum
  156. Postgre terribly slow
  157. Version Change
  158. DB benchmark and pg config file help
  159. Re: Configuration Advice
  160. Monitoring Transaction Log size
  161. Raid 10 or Raid 5 on Dell PowerEdge
  162. Table Inheritence and Partioning
  163. PG8.2.1 choosing slow seqscan over idx scan
  164. Table Size
  165. Re: Caching in PostgreSQL
  166. Caching in PostgreSQL
  167. FiberChannel cards for FreeBSD on AMD64
  168. pg_trgm performance
  169. Re: max() versus order/limit (WAS: High update
  170. Re: max() versus order/limit (WAS: High update activity, PostgreSQL vs BigDBMS)
  171. Re:
  172. Problem with grouping, uses Sort and GroupAggregate, HashAggregate is better(?)
  173. Performance of Parser?
  174. Physical separation of tables and indexes - where pg_xlogshould go?
  175. Large table performance
  176. Partitioning
  177. Planner statistics, correlations
  178. Improving SQL performance
  179. unusual performance for vac following 8.2 upgrade
  180. Does it matters the column order in indexes and constraints creation?
  181. Slow inner join, but left join is fast
  182. Re: group by will not use an index?
  183. group by will not use an index?
  184. High inserts, bulk deletes - autovacuum vs scheduled vacuum
  185. Re: Horribly slow query/ sequential scan
  186. Running PG on cluster files systems
  187. Re: Horribly slow query/ sequential scan
  188. Horribly slow query/ sequential scan
  189. MI5 Persecution: Security Service Tribunal Denies
  190. tweaking under repeatable load
  191. table partioning performance
  192. Missing the point of autovacuum
  193. Re: Partitioning
  194. Partitioning
  195. Slow Query on Postgres 8.2
  196. MI5 Persecution: Communications with Security Service Tribunal in 1999
  197. PostgreSQL to host e-mail?
  198. MI5 Persecution: Eye Say, and Lord Gnome Answers
  199. MI5 Persecution: Counter-surveillance sweep by Nationwide Investigations Group
  200. Trivial function query optimized badly
  201. Performance of PostgreSQL on Windows vs Linux
  202. More 8.2 client issues (Was: [Slow dump?)
  203. Max Connections to a New Hardware
  204. Slow dump?
  205. Config parameters
  206. what work_mem needs a query needs?
  207. glibc double-free error
  208. Worse perfomance on 8.2.0 than on 7.4.14
  209. Re: Worse perfomance on 8.2.0 than on 7.4.14
  210. Re: Backup/Restore too slow
  211. Postgresql Configutation and overflow
  212. performance implications of binary placement
  213. Postgresql Configutation and overflow
  214. High update activity, PostgreSQL vs BigDBMS
  215. Re: [GENERAL] Need Help
  216. Re: [NOVICE] Partitioning
  217. Questions about planner methods
  218. What you would consider as heavy traffic?
  219. URGENT: Out of disk space pg_xlog
  220. Question: Clustering & Load Balancing
  221. GROUP BY vs DISTINCT
  222. max_fsm_pages and check_points
  223. Inner join vs where-clause subquery
  224. Query plan changing when queried data does not
  225. transaction ID wrap limit
  226. Optimizing timestamp queries? Inefficient Overlaps?
  227. Scaling concerns
  228. partition text/varchar check problem
  229. opportunity to benchmark a quad core Xeon
  230. Dell 2900/Xeon 5000 ?
  231. unsubscribe
  232. EXPLAIN ANALYZE on 8.2
  233. Two tables in one
  234. Optimizing a query
  235. strange query behavior
  236. Insertion to temp table deteriorating over time
  237. Slow update with simple query
  238. really quick multiple inserts can use COPY?
  239. Re: really quick multiple inserts can use COPY?
  240. Re: really quick multiple inserts can use COPY?
  241. Looking for hw suggestions for high concurrency OLTP app
  242. Re: Postgresql - Threshold value.
  243. Re: Postgresql - Threshold value.
  244. Postgresql - Threshold value.
  245. New to PostgreSQL, performance considerations
  246. Re: Low throughput of binary inserts from windows to linux
  247. Advice on selecting good values for work_mem?
  248. Re: Advice on selecting good values for work_mem?
  249. How to determine if my setting for shared_buffers is too high?
  250. One table is very slow, but replicated table (same data) is fine