Mailing lists [pgsql-performance]

29 August 2003

• 00:11   bad estimates / non-scanning aggregates Ken Geis
• 00:50   Re: Queries sometimes take 1000 times the normal time Anders K. Pedersen
• 01:13   Taking another shot at the PostgreSQL/filesystem benchmarks Bill Moran
• 01:20   Re: The results of my PostgreSQL/filesystem performance Bill Moran
• 01:37   Re: The results of my PostgreSQL/filesystem performance Christopher Kings-Lynne
• 01:57   Re: The results of my PostgreSQL/filesystem performance tests Christopher Kings-Lynne
• 02:00   Re: opinion on RAID choice Vivek Khera
• 02:15   Re: The results of my PostgreSQL/filesystem performance Bill Moran
• 02:45   Re: bad estimates / non-scanning aggregates Bruno Wolff III
• 02:51   Re: bad estimates / non-scanning aggregates Ken Geis
• 02:56   Re: bad estimates / non-scanning aggregates Bruno Wolff III
• 03:01   Re: bad estimates / non-scanning aggregates Ken Geis
• 03:32   Re: bad estimates / non-scanning aggregates Bruno Wolff III
• 03:40   PostgreSQL HDD Grow capacity Eko Pranoto
• 03:46   Re: bad estimates Ken Geis
• 03:59   Re: bad estimates Bruno Wolff III
• 04:09   Re: bad estimates Ken Geis
• 04:19   Re: bad estimates Bruno Wolff III
• 04:24   Re: opinion on RAID choice scott.marlowe
• 06:50   Indexing question Alexander Priem
• 07:01   Re: bad estimates Ken Geis
• 07:03   Re: Indexing question Christopher Kings-Lynne
• 07:04   Re: Indexing question Tomasz Myrta
• 07:22   Re: Hardware recommendations to scale to silly load William Yu
• 07:27   Re: Hardware recommendations to scale to silly load Christopher Kings-Lynne
• 07:47   Re: Indexing question Alexander Priem
• 07:57   Re: bad estimates Ken Geis
• 07:59   Re: Indexing question Tomasz Myrta
• 08:10   Re: bad estimates Ken Geis
• 08:11   Re: Indexing question Christopher Kings-Lynne
• 08:11   Re: bad estimates Christopher Kings-Lynne
• 08:16   Re: Hardware recommendations to scale to silly load Shridhar Daithankar
• 08:17   Re: bad estimates Ken Geis
• 08:28   Re: Queries sometimes take 1000 times the normal time Shridhar Daithankar
• 08:39   Re: Indexing question Alexander Priem
• 08:57   Re: Indexing question Tomasz Myrta
• 09:07   Re: Indexing question Alexander Priem
• 12:05   Re: Hardware recommendations to scale to silly load Ron Johnson
• 12:50   Force table to be permanently in cache? Fabian Kreitner
• 12:53   Re: bad estimates Jeff
• 13:55   PL/pgSQL functions - text / varchar - havy performance issue?! Oliver Siegmar
• 14:00   Re: Indexing question Tom Lane
• 14:05   Re: Hardware recommendations to scale to silly load Andrew Sullivan
• 14:35   Re: Force table to be permanently in cache? Andrew Sullivan
• 14:47   Re: PL/pgSQL functions - text / varchar - havy performance Bill Moran
• 15:02   Re: PL/pgSQL functions - text / varchar - havy performance Andrew Sullivan
• 15:02   Re: PL/pgSQL functions - text / varchar - havy performance issue?! Oliver Siegmar
• 15:03   Re: bad estimates Stephan Szabo
• 15:12   Re: Indexing question Alexander Priem
• 15:35   Re: PL/pgSQL functions - text / varchar - havy performance Bill Moran
• 15:54   Re: PL/pgSQL functions - text / varchar - havy performance Andrew Sullivan
• 16:07   Re: bad estimates Ken Geis
• 16:18   Re: PL/pgSQL functions - text / varchar - havy performance Tom Lane
• 16:27   2.4 v/s 2.6 again. Shridhar Daithankar
• 16:37   Re: bad estimates Sean Chittenden
• 16:52   Re: Hardware recommendations to scale to silly load William Yu
• 16:59   Re: Indexing question Richard Ellis
• 17:00   Re: bad estimates Ken Geis
• 17:04   Re: bad estimates Sean Chittenden
• 17:20   sourcecode for newly release eRServer? george young
• 17:32   Re: Hardware recommendations to scale to silly load Ron Johnson
• 18:51   Re: sourcecode for newly release eRServer? Andrew Sullivan
• 21:00   SQL performance problems Rhaoni Chiu Pereira
• 22:04   Re: SQL performance problems Tom Lane