- REPOST: Performance improves only after repeated VACUUM/ANALYZE
- Re: Low CPU Usage
- Re: Tablespaces and NFS
- Re: Tablespaces and NFS
- Query works when kludged, but would prefer "best practice" solution
- DELETE queries slow down
- update command question?
- Watch Satellite TV On Your PC
- Regarding COPY command from Postgres 8.2.0
- Index files
- Long Running Commits - Not Checkpoints
- Clustered tables improves perfs ?
- Index usage when bitwise operator is used
- db performance/design question
- pg_dump blocking create database?
- efficient pattern queries (using LIKE, ~)
- 500rows = 1min/2.5k rows=20min/6K rows 2 hours and still running
- More Vacuum questions...
- Barcelona vs Tigerton
- [Again] Postgres performance problem
- What to vacuum after deleting lots of tables
- random_page_costs - are defaults of 4.0 realistic for SCSI RAID 1
- Re: DRBD and Postgres: how to improve the perfomance?
- DRBD and Postgres: how to improve the perfomance?
- postgres memory management issues?
- How planner decides left-anchored LIKE can use index
- Reasonable amount of indices
- postgres memory management issues?
- Re: Hardware spec]
- Re: [ADMIN] ADO -PostgreSQL OLE DB Provider
- SAN vs Internal Disks
- Hardware spec
- GIST performance (PostGIS): the_geom vs. Envelope(the_geom)
- utilising multi-cpu/core machines?
- Re : optimize query with a maximum(date) extraction
- optimize query with a maximum(date) extraction
- Performance on 8CPU's and 32GB of RAM
- join tables vs. denormalization by trigger
- About autovacuum
- Vacum Analyze problem
- Re: [GENERAL] Performance issue with nested loop
- Slow Query
- schemas to limit data access
- schemas to limit data access
- 8.2 Autovacuum BUG ?
- Transaction Log
- Transaction Log
- LIKE query verses =
- Performance issue with nested loop
- Performance problem with table containing a lot of text (blog)
- Re: 8.2 Query 10 times slower than 8.1 (view-heavy)
- 8.2 Query 10 times slower than 8.1 (view-heavy)
- 8.2.4 Chooses Bad Query Plan
- Bitmap Heap Scan before using index
- Performance issue
- Performance across multiple schemas
- index & Bitmap Heap Scan
- server performance issues - suggestions for tuning
- Performance issue
- Postgres performance problem
- Shared memory usage
- MI5 Persecution: Neil Fox (March/1998) (5999)
- MI5 Persecution: Capital Radio (11/April/1997) (4776)
- MI5 Persecution: GLR: David Hepworth (9/May/1997) (3553)
- MI5 Persecution: GLR: David Hepworth (21/Feb/1997) (2330)
- MI5 Persecution: Life is so hard (1107)
- MI5 Persecution: BBC1 TV News - 18/Dec/2002 (8445)
- MI5 Persecution: Channel Four TV News - 10/April/2002 (7222)
- MI5 Persecution: BBC-TV See You, See Me - 7/Dec/2001 (5999)
- MI5 Persecution: C4 SnowMail - January/2001 (4776)
- MI5 Persecution: England expects every man to do his duty (3553)
- MI5 Persecution: Nicholas Witchell - 10/April/1999 (2330)
- MI5 Persecution: Chris Tarrant - 10/March/1999 (1107)
- Partioning tsearch2 a table into chunks and accessing via views
- significant vacuum issues - looking for suggestions
- partitioned table and ORDER BY indexed_field DESC LIMIT 1
- deadlock_timeout parameter in Postgresql.cof
- deadlock_timeout parameter in Postgresql.cof
- long-running query - needs tuning
- Installing PostgreSQL
- asynchronous commit feature
- Re: Long running transaction in pg_activity_log
- Long running transaction in pg_activity_log
- Fast tsearch2, trigram matching on short phrases
- io storm on checkpoints, postgresql 8.2.4, linux
- Poor Performance after Upgrade
- Optimising "in" queries
- Re: Autovacuum is running forever
- Autovacuum is running forever
- MI5 Persecution: Channel Four TV News - 12/Feb/1999 (5999)
- MI5 Persecution: Dimbleby / John Major, April 1997 (4776)
- MI5 Persecution: Ken Clarke (2), April 1997 (3553)
- MI5 Persecution: Ken Clarke (1), April 1997 (2330)
- MI5 Persecution: Overview (1107)
- MI5 Persecution: David Hepworth (2) 16/5/97 (18229)
- MI5 Persecution: Victor Lewis-Smith 9/5/97 (17006)
- MI5 Persecution: Continuing Silence 9/5/97 (15783)
- Re: Terminology Question
- MI5 Persecution: Peak Practice 26/4/97 (14560)
- MI5 Persecution: I am being ignored 17/4/97 (13337)
- MI5 Persecution: Striking out action 10/3/97 (12114)
- MI5 Persecution: David Hepworth (1) 26/2/97 (10891)
- MI5 Persecution: No Justice 20/11/96 (9668)
- MI5 Persecution: WTGROMT 18/11/96 (8445)
- MI5 Persecution: Excellent web page 19/10/96 (7222)
- MI5 Persecution: Usual targets of such abuse 10/10/96 (5999)
- MI5 Persecution: Just too crazy 30/9/96 (4776)
- MI5 Persecution: Latest technology 31/7/96 (3553)
- MI5 Persecution: BBC+ITN=MI5 23/7/96 (2330)
- MI5 Persecution: Silly-billy 6/7/96 (1107)
- MI5 Persecution: Silly-billy 6/7/96 (5999)
- MI5 Persecution: Old_500 5/7/96 (4776)
- MI5 Persecution: alt.fan.mike-corley 6/6/96 (3553)
- MI5 Persecution: Bernard Levin 1/6/96 (2330)
- MI5 Persecution: Fitted up 26/4/96 (1107)
- Re: [pgsql-jobs] Looking for database hosting
- Re: [pgsql-jobs] Looking for database hosting
- MI5 Persecution: Fitted up 26/4/96 (1107)
- schema design question
- Re: Help optimize view
- Re: Help optimize view
- Re: Fwd: Table Partitioning
- Performance Solaris vs Linux
- Raid Configurations
- Stable function optimisation
- Bad planner decision - bitmap scan instead of index
- Integrated perc 5/i
- Indexscan is only used if we use "limit n"
- RAID 10 or RAID 10 + RAID 1
- Stable function optimisation
- Proposal: Pluggable Optimizer Interface
- Re: Performance on writable views
- Bitmap Index Scan optimization opportunity
- Re: Help optimize view
- Performance of CREATE INDEX
- Dell Hardware Recommendations
- mid 2007 "best bang for the buck" hardware opinions
- How to ENABLE SQL capturing???
- select count(*) performance
- Update table performance
- Planner making wrong decisions 8.2.4. Insane cost calculations.
- Extreme slow select query 8.2.4
- Default Performance between 8.0 and 8.1
- Postgres optimizer
- Performance problems with large telemetric datasets on 7.4.2
- Why are distinct and group by choosing different plans?
- cpu throttling
- Semantics of PostgreSQL Server Log Stats
- Using EXECUTE in a function
- Seq scan on join table despite index and high statistics
- one left join screws up the query
- Query optimization....
- Re: Postgres configuration for 64 CPUs, 128 GB RAM...
- Questions on Tags table schema
- Re: Slow query with backwards index scan
- select on 1milion register = 6s
- Re: Slow query with backwards index scan
- Vacuum looping?
- Slow query with backwards index scan
- Re: update, truncate and vacuum
- update, truncate and vacuum
- disk filling up
- performance of postgresql in replication using slony
- Insert Statements Hanging
- Affect of Reindexing on Vacuum Times
- Re: [pgsql-advocacy] 8.2 -> 8.3 performance numbers
- Performance issue with 8.2.3 - "C" application
- Re: 8.2 -> 8.3 performance numbers
- Re: Table Statistics with pgAdmin III
- index over timestamp not being used
- Table Statistics with pgAdmin III
- Query performance issue
- Re: multicolumn index column order
- Re: multicolumn index column order
- Second SpecJAppserver2004 with PostgreSQL
- multicolumn index column order
- Simple select hangs while CPU close to 100%
- Slow select performance when filter with function
- Simple query showing 270 hours of CPU time
- Problems with posting
- Improving select peformance
- Trying to tune postgres, how is this config?
- Is it possible to know where is the "deadlock"
- User concurrency thresholding: where do I look?
- Optmal tags design?
- When/if to Reindex
- Re: Parrallel query execution for UNION ALL Queries
- How to use a trigger to write rows to a remote server
- Closed ports hanging around on Windows
- ionice to make vacuum friendier?
- importance of fast disks with pg
- insert vs select into performance
- large number of connected connections to postgres database (v8.0)
- Postgres configuration for 64 CPUs, 128 GB RAM...
- slony over VPN and LAN
- slony over LAN and VPN
- Vacuum full considered useful ;)
- FORGOT TO CONFIGURE RAID! DELL POWEREDGE 2950
- Database Statistics???
- one column from huge view
- Estimating WAL volume
- TRUNCATE TABLE
- bitmap-index-scan slower than normal index scan
- Weird row estimate
- Two questions.. shared_buffers and long reader issue
- TIMING A QUERY ???
- WALL on controller without battery?
- Re: PostgreSQL publishes first real benchmark
- best use of an EMC SAN
- tuning a function to insert/retrieve values from a reference table
- Query Analyser
- PostgreSQL publishes first real benchmark
- Advice about how to delete
- Performance of PostgreSQL and Oracle
- Direct I/O
- Best query approach
- improvement suggestions for performance design
- Query is taking 5 HOURS to Complete on 8.1 version
- Filesystem Direct I/O and WAL sync option
- Delete Cascade FK speed issue
- poor use of indexes / feature: add OnlyUseIndex join/query plan hint?
- Join with lower/upper limits doesn't scale well
- kill off idle connections?
- Resource to learn code and share code and knowledge
- slow query
- [PERFORMANCE] is it possible to force an index to be held in memory?
- How to install Postgresql 8.2.x on windows XP silently
- Re: PostgreSQL 8.0 occasionally slow down
- PostgreSQL 8.0 occasionally slow down
- update query taking too long
- High IOWAIT times, low iops? Need Help with configuration
- rtree/gist index taking enormous amount of space in 8.2.3
- Re:
- Re:
- Non-optimal query plan with 8.2
- startup caching suggestions
- Is AIX Concurrent IO safe with PostgreSQL?
- Re: PREPARE and stuff
- PREPARE and stuff
- MI5 Persecution: Stasi 21/4/96 (16304)
- MI5 Persecution: Leant On 7/4/96 (14790)
- MI5 Persecution: Shoot to Kill 4/4/96 (13276)
- MI5 Persecution: Email Cruelty 11/3/96 (11762)
- MI5 Persecution: Jeff Rooker MP 5/3/96 (10248)
- MI5 Persecution: Flight or fight 7/1/96 (8734)
- MI5 Persecution: A new Kafka? 3/10/95 (5706)
- MI5 Persecution: Do they fear truth? 3/10/95 (4192)
- MI5 Persecution: Grievous Bodily Harm 2/10/95 (2678)
- MI5 Persecution: Goldfish and Piranha 29/9/95 (1164)
- Slow join query