Group: pgsql.performance
Back
Available subjects:
Slow Query
(1 messages)
Reasonable amount of indices
(1 messages)
How planner decides left-anchored LIKE can use index
(1 messages)
postgres memory management issues?
(1 messages)
DRBD and Postgres: how to improve the perfomance?
(1 messages)
What to vacuum after deleting lots of tables
(1 messages)
Re: 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
(2 messages)
pg_dump blocking create database?
(1 messages)
Long Running Commits - Not Checkpoints
(1 messages)
Index files
(1 messages)
Watch Satellite TV On Your PC
(1 messages)
Index usage when bitwise operator is used
(1 messages)
Query works when kludged, but would prefer "best practice" solution
(2 messages)
Linux mis-reporting memory
(1 messages)
Searching for the cause of a bad plan
(5 messages)
Query planner unaware of possibly best plan
(1 messages)
Possible explanations for catastrophic performace deterioration?
(1 messages)
Incorrect row estimates in plan?
(2 messages)
sequence query performance issues
(1 messages)
OOM Errors as a result of table inheritance and a bad plan(?)
(1 messages)
Query taking too long. Problem reading explain output.
(1 messages)
can't shrink relation
(2 messages)
Partitioning in postgres - basic question
(1 messages)
quickly getting the top N rows
(2 messages)
query plan worse after analyze
(1 messages)
hashjoin chosen over 1000x faster plan
(3 messages)
Huge amount of memory consumed during transaction
(4 messages)
Performance problems with prepared statements
(1 messages)
How to speed up min/max(id) in 50M rows table?
(3 messages)
Vacuum goes worse
(5 messages)
Autovacuum running out of memory
(2 messages)
Incorrect estimates on columns
(2 messages)
need help with a query
(1 messages)
12 hour table vacuums
(1 messages)
Finalizing commit taking very long
(2 messages)
Bunching "transactions"
(1 messages)
[HACKERS] 8.3beta1 testing on Solaris
(4 messages)
partitioned table and ORDER BY indexed_field DESC LIMIT 1
(2 messages)
Speed difference between select ... union select ... and select from partitioned_table
(1 messages)
partitioned table and ORDER BY indexed_field DESCLIMIT 1
(1 messages)
Outer joins and Seq scans
(2 messages)
Improving Query
(1 messages)
Two fast queries get slow when combined
(1 messages)
[Fwd: Re: Outer joins and Seq scans]
(2 messages)
select max(field) from table much faster with a group by clause?
(3 messages)
How to avoid hashjoin and mergejoin
(1 messages)
Union within View vs.Union of Views
(1 messages)
"MixedCase sensitive quoted" names
(1 messages)
Which index methodology is better?-
(1 messages)
Is ANALYZE transactional?
(1 messages)
Estimation problem with a LIKE clause containing a /
(6 messages)
Need to run CLUSTER to keep performance
(1 messages)
Join performance
(5 messages)
[HACKERS] Estimation problem with a LIKE clause containing a /
(2 messages)
Help understanding stat numbers
(1 messages)
Curious about dead rows.
(2 messages)
difference between a unique constraint and a unique index ???
(1 messages)
ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
(1 messages)
=?windows-1256?Q?Performance_problem_(outer_join_+_view_+_non-strict_func?= =?windows-1256?Q?tions)=FE?=
(1 messages)
autovacuum: recommended?
(1 messages)
Performance problem with UNION ALL view and domains
(1 messages)
Base de Datos Transaccional
(1 messages)
PostgreSQL performance on various distribution stock kernels
(1 messages)
Query only slow on first run
(5 messages)
GiST indexing tuples
(1 messages)
TB-sized databases
(6 messages)
MI5 Persecution: How to Identify the Persecutors (2611)
(1 messages)
EXPLAIN ANALYZE time calculations
(2 messages)
Optimizer Not using the Right plan
(1 messages)
Trouble with LEFT JOIN using VIEWS.
(1 messages)
Combining two bitmap scans out performs a single regular index scan?
(1 messages)
libgcc double-free, backend won't die
(5 messages)
database tuning
(2 messages)
Heavy write activity on first vacuum of fresh TOAST data
(3 messages)
Heavy write activity on first vacuum of fresh TOASTa
(1 messages)
VACUUM FREEZE output more than double input
(1 messages)
explanation for seeks in VACUUM
(1 messages)
1