Mailing lists [pgsql-performance]

16 January 2020

• 16:21   Queries in plpgsql are 6 times slower on partitioned tables Marcin Barczyński
• 17:06   Bad query plan decision when using multiple column index - postgresqluses only first column then filters Cosmin Prund
• 18:11   Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane
• 19:59   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Michael Lewis
• 20:18   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Cosmin Prund
• 20:27   Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane
• 21:15   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Cosmin Prund
• 21:20   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Laurenz Albe
• 21:23   Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane
• 21:52   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Michael Lewis
• 21:55   Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane
• 22:06   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Cosmin Prund
• 22:52   Re: Bad query plan decision when using multiple column index -postgresql uses only first column then filters Cosmin Prund