Mailing lists [pgsql-performance]

29 October 2009

• 09:54   Re: sub-select in IN clause results in sequential scan Grzegorz Jaśkiewicz
• 10:33   Re: sub-select in IN clause results in sequential scan Angayarkanni
• 14:10   Re: sub-select in IN clause results in sequential scan Anj Adu
• 14:28   Re: query planning different in plpgsql? Michal J. Kubski
• 14:32   Re: Postgresql optimisation Denis BUCHER
• 14:32   Re: query planning different in plpgsql? Michal J. Kubski
• 15:12   database size growing continously Peter Meszaros
• 15:25   Re: bitmap heap scan way cheaper than seq scan on the same amount of tuples (fts-search). Tom Lane
• 15:29   Re: sub-select in IN clause results in sequential scan Bob Lunney
• 15:34   Re: database size growing continously Ludwik Dylag
• 15:35   Re: sub-select in IN clause results in sequential scan Robert Haas
• 15:40   Re: sub-select in IN clause results in sequential scan Anj Adu
• 15:42   Re: database size growing continously Josh Rovero
• 16:00   Re: database size growing continously Matthew Wakeling
• 16:01   Re: database size growing continously Ludwik Dylag
• 16:14   Re: database size growing continously Chris Ernst
• 16:15   Re: database size growing continously Joshua D. Drake
• 16:21   Re: database size growing continously Steve Crawford
• 16:40   Re: database size growing continously Steve Crawford
• 16:44   Re: query planning different in plpgsql? Scott Carey
• 17:00   Re: database size growing continously Scott Marlowe
• 20:53   Modeling a table with arbitrary columns Andreas Hartmann
• 21:25   Re: Modeling a table with arbitrary columns Thomas Kellerer
• 22:14   Re: database size growing continously Joshua D. Drake
• 22:25   Re: optimizing query with multiple aggregates Doug Cole