• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-cygwin
    • pgsql-general
    • pgsql-interfaces
    • pgsql-jdbc
    • pgsql-jobs
    • pgsql-novice
    • pgsql-odbc
    • pgsql -performance
    • pgsql-php
    • pgsql-ports
    • pgsql-sql
  • Developer lists
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-performance 2006-03 Chronological Index (3/4)

• Thread Index
• [Prev Page]
• [Next Page]

• 17 March 2006
  • Re: 1 TB of memory Luke Lonergan
  • Re: Help optimizing a slow index scan Evgeny Gridasov
  • Re: Background writer configuration Evgeny Gridasov
  • Re: Help optimizing a slow index scan Merlin Moncure
  • Re: Background writer configuration 11
  • Re: Help optimizing a slow index scan Bruno Wolff III
  • Re: 1 TB of memory Jim C. Nasby
  • Re: Background writer configuration Steinar H. Gunderson
  • Re: Background writer configuration Steve Atkins
  • Re: Help optimizing a slow index scan Merlin Moncure
  • Re: Help optimizing a slow index scan Dan Harris
  • Re: Help optimizing a slow index scan Dan Harris
  • Re: Background writer configuration Kevin Grittner
  • Re: 1 TB of memory Merlin Moncure
  • Re: Background writer configuration PFC
  • Re: Background writer configuration Evgeny Gridasov
  • Re: 1 TB of memory Merlin Moncure
  • Re: 1 TB of memory Alex Stapleton
  • Re: 1 TB of memory Rodrigo Madera
  • Re: Background writer configuration PFC
  • Re: 1 TB of memory Michael Stone
  • Re: 1 TB of memory Luke Lonergan
  • Re: Background writer configuration Evgeny Gridasov
  • planner with index scan cost way off actual cost, advices to tweak cost constants? Guillaume Cottenceau
  • Re: Indexes with descending date columns andrew
  • Re: 1 TB of memory Josh Berkus
  • Re: 1 TB of memory Luke Lonergan
  • Re: 1 TB of memory Luke Lonergan
• 16 March 2006
  • Re: Background writer configuration Kevin Grittner
  • Re: Help optimizing a slow index scan Dan Harris
  • Help optimizing a slow index scan Dan Harris
  • Re: 1 TB of memory Matthew Nuzum
  • Re: 1 TB of memory Ron Peacetree
  • Indexes with descending date columns Theo Kramer
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
  • Re: BETWEEN optimizer problems with single-value Tom Lane
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
  • Re: BETWEEN optimizer problems with single-value Alvaro Herrera
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
  • Re: 1 TB of memory Joshua D. Drake
  • 1 TB of memory Jim Nasby
  • Re: Background writer configuration Evgeny Gridasov
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: PostgreSQL and Xeon MP Sven Geisler
  • Re: PostgreSQL and Xeon MP Tom Lane
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: BETWEEN optimizer problems with single-value Tom Lane
  • Re: PostgreSQL and Xeon MP Sven Geisler
  • Re: PostgreSQL and Xeon MP Tom Lane
  • Re: PostgreSQL and Xeon MP Kenneth Marshall
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: PostgreSQL and Xeon MP Richard Huxton
  • Re: PostgreSQL and Xeon MP Sven Geisler
  • Re: PostgreSQL and Xeon MP Guillaume Smet
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
  • Re: PostgreSQL and Xeon MP Richard Huxton
  • PostgreSQL and Xeon MP Guillaume Smet
  • Re: BETWEEN optimizer problems with single-value Tom Lane
  • Re: Slow SELECTS after large update cycle Jan de Visser
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
  • Re: BETWEEN optimizer problems with single-value Simon Riggs
• 15 March 2006
  • Re: [HACKERS] BETWEEN optimizer problems with single-value Kevin Grittner
  • Re: Slow SELECTS after large update cycle Simon Riggs
  • Re: Slow SELECTS after large update cycle Chris
  • Re: [HACKERS] BETWEEN optimizer problems with single-value range Simon Riggs
  • Re: BETWEEN optimizer problems with single-value range Merlin Moncure
  • Re: BETWEEN optimizer problems with single-value range Andreas Kretschmer
  • Re: Background writer configuration Kevin Grittner
  • Re: BETWEEN optimizer problems with single-value Kevin Grittner
  • Re: Background writer configuration Joshua D. Drake
  • Background writer configuration Kevin Grittner
  • Slow SELECTS after large update cycle Jan de Visser
  • Re: BETWEEN optimizer problems with single-value range Merlin Moncure
  • Re: BETWEEN optimizer problems with single-value Tom Lane
  • Re: BETWEEN optimizer problems with single-value Kevin Grittner
  • Re: VACUUM FULL hangs Marcin Mańk
  • Re: BETWEEN optimizer problems with single-value range Andreas Kretschmer
  • BETWEEN optimizer problems with single-value range Kevin Grittner
  • Re: VACUUM FULL hangs Richard Huxton
  • VACUUM FULL hangs Marcin Mańk
  • Re: x206-x225 Richard Huxton
• 14 March 2006
  • Re: Vacuum template databases, Urgent: Production probl Vivek Khera
  • Re: x206-x225 Jim C. Nasby
  • Re: x206-x225 Richard Huxton
  • Re: Vacuum template databases, Urgent: Production probl Jim C. Nasby
  • Re: Vacuum template databases, Urgent: Production probl mcelroy, tim
  • Re: Vacuum template databases, Urgent: Production probl Jim C. Nasby
  • Re: Vacuum template databases, Urgent: Production problem Jim C. Nasby
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Jim C. Nasby
  • Re: x206-x225 Jim C. Nasby
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Jim C. Nasby
  • Re: Process Time X200 Jim C. Nasby
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Merlin Moncure
  • firebird X postgresql 8.1.2 windows, performance comparison andremachado
  • Re: Vacuum template databases, Urgent: Production probl mcelroy, tim
  • Re: Vacuum template databases, Urgent: Production problem Tom Lane
  • Vacuum template databases, Urgent: Production problem Pallav Kalva
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Merlin Moncure
  • Re: PG Statistics mcelroy, tim
  • Re: PG Statistics mcelroy, tim
  • firebird X postgresql 8.1.2 windows, performance comparison andremachado
  • Re: import performance Chris
  • Re: import performance David Lang
  • Re: import performance Chris
  • Re: import performance Frank Wiles
  • Re: import performance Tom Lane
  • Re: import performance Chris
  • Re: import performance Frank Wiles
  • Re: import performance Chris
  • Re: import performance Gavin Sherry
  • Re: import performance Dave Dutcher
  • Re: PG Statistics Steve Poe
  • Re: import performance Gavin Sherry
  • import performance Chris
  • Re: PG Statistics Michael Fuhr
• 13 March 2006
  • PG Statistics mcelroy, tim
  • Re: firebird X postgresql 8.1.2 windows, performance Scott Marlowe
  • Re: No vacuum for insert-only database? Josh Berkus
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Josh Berkus
  • Re: No vacuum for insert-only database? Bruno Wolff III
  • firebird X postgresql 8.1.2 windows, performance comparison andremachado
  • Re: No vacuum for insert-only database? Alvaro Herrera
  • Re: No vacuum for insert-only database? Craig A. James
  • Re: No vacuum for insert-only database? Alvaro Herrera
  • No vacuum for insert-only database? Craig A. James
  • unsubscribe Nick Howden
  • Re: Query time PFC
  • Re: Query time Ruben Rubio Rey
• 12 March 2006
  • Re: help needed asap.... Bruno Wolff III
  • Re: help needed asap.... Matthew Nuzum
  • help needed asap.... Phadnis
• 11 March 2006
  • Re: Postgres and Ingres R3 / SAN Josh Berkus
  • Re: x206-x225 David Lang
  • Re: x206-x225 Joost Kraaijeveld
  • Re: x206-x225 Tom Lane
  • Re: x206-x225 Joost Kraaijeveld
  • Re: x206-x225 PFC
  • Re: x206-x225 Joost Kraaijeveld
  • Re: x206-x225 David Lang
  • Re: x206-x225 Joost Kraaijeveld
  • Re: firebird X postgresql 8.1.2 windows, performance comparison Chris Travers
  • firebird X postgresql 8.1.2 windows, performance comparison Andre Felipe Machado
• 10 March 2006
  • Re: Trouble managing planner for timestamptz columns Tom Lane
  • Re: Trouble managing planner for timestamptz columns Marc Morin
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: one-field index vs. multi-field index planner Tom Lane
  • Re: Hanging queries on dual CPU windows Magnus Hagander
  • Re: Trouble managing planner for timestamptz columns Tom Lane
  • Trouble managing planner for timestamptz columns Marc Morin
  • Re: one-field index vs. multi-field index planner Evgeny Gridasov
  • Re: one-field index vs. multi-field index planner estimates Tom Lane
  • Re: Process Time X200 Scott Marlowe
  • one-field index vs. multi-field index planner estimates Evgeny Gridasov
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: Process Time X200 Matthew Nuzum
  • Re: Query time Jim C. Nasby
  • Re: Using materialized views for commonly-queried subsets Jim C. Nasby
  • Re: pg_reset_stats + cache I/O % Jim C. Nasby
  • Re: Hanging queries on dual CPU windows Magnus Hagander
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: Hanging queries on dual CPU windows Hakan Kocaman
  • Re: x206-x225 Daniel Blaisdell
  • Re: Query time Richard Huxton
  • Re: x206-x225 Richard Huxton
  • Re: Hanging queries on dual CPU windows Jan de Visser
  • Re: Query time Ruben Rubio Rey
  • Re: Process Time X200 PFC
  • Re: Query time Michael Fuhr
  • Re: Process Time X200 NbForYou
  • Re: Query time Ruben Rubio Rey
  • Re: Process Time X200 Richard Huxton
  • Query time Ruben Rubio Rey
  • FW: x206-x226 H.J. Sanders
  • x206-x225 H.J. Sanders
  • Re: Process Time X200 Ragnar

• Thread Index
• [Prev Page]
• [Next Page]