Mailing lists [pgsql-performance]

1 June 2023

• 06:36   thousands of CachedPlan entry per backend James Pang (chaolpan)
• 09:53   Re: thousands of CachedPlan entry per backend Laurenz Albe
• 10:18   Re: thousands of CachedPlan entry per backend Pavel Stehule
• 11:50   RE: thousands of CachedPlan entry per backend James Pang (chaolpan)
• 15:48   Re: thousands of CachedPlan entry per backend Laurenz Albe
• 17:26   Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server Sergio Rus

2 June 2023

• 04:45   RE: thousands of CachedPlan entry per backend James Pang (chaolpan)
• 07:56   Re: thousands of CachedPlan entry per backend Pavel Stehule
• 12:06   RE: thousands of CachedPlan entry per backend James Pang (chaolpan)
• 22:17   Re: thousands of CachedPlan entry per backend Jeff Janes

3 June 2023

• 10:18   Understand time taken by individual SQL statements in a procedure Satalabaha Postgres
• 10:36   Re: Understand time taken by individual SQL statements in a procedure Julien Rouhaud
• 20:46   Re: Understand time taken by individual SQL statements in a procedure Satalabaha Postgres

4 June 2023

• 11:34   Weird behavior of INSERT QUERY Satalabaha Postgres
• 11:40   Re: Weird behavior of INSERT QUERY Satalabaha Postgres
• 14:21   Re: Weird behavior of INSERT QUERY Julien Rouhaud
• 14:42   Re: Weird behavior of INSERT QUERY Satalabaha Postgres
• 16:21   Re: Weird behavior of INSERT QUERY Julien Rouhaud
• 16:26   Re: Weird behavior of INSERT QUERY Tom Lane
• 17:16   Re: Weird behavior of INSERT QUERY Ranier Vilela
• 17:49   Re: Weird behavior of INSERT QUERY Satalabaha Postgres
• 17:58   Re: Weird behavior of INSERT QUERY Satalabaha Postgres

5 June 2023

• 02:05   Re: Weird behavior of INSERT QUERY Ranier Vilela
• 14:55   Re: Weird behavior of INSERT QUERY Satalabaha Postgres

9 June 2023

• 11:36   wrong rows estimation by hash join James Pang (chaolpan)

10 June 2023

• 23:38   Re: wrong rows estimation by hash join Tomas Vondra

12 June 2023

• 11:09   Postgresql equal join on function with columns not use index James Pang (chaolpan)
• 16:18   Re: Postgresql equal join on function with columns not use index Tom Lane
• 17:20   RE: Postgresql equal join on function with columns not use index James Pang (chaolpan)
• 23:17   Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT benoit
• 23:34   Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT Peter Geoghegan
• 23:50   RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT benoit
• 23:55   Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT Chris Hoover

13 June 2023

• 00:34   RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT benoit
• 03:09   Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT Chris Hoover
• 12:21   extended statistics n-distinct on multiple columns not used when join two tables James Pang (chaolpan)
• 12:29   Re: extended statistics n-distinct on multiple columns not used when join two tables Pavel Stehule
• 16:50   Re: Postgresql equal join on function with columns not use index Tom Lane
• 17:17   Re: Postgresql equal join on function with columns not use index Pavel Stehule
• 18:00   Re: Postgresql equal join on function with columns not use index Pavel Stehule

15 June 2023

• 11:32   RE: Postgresql equal join on function with columns not use index James Pang (chaolpan)
• 11:35   Re: Postgresql equal join on function with columns not use index Pavel Stehule

17 June 2023

• 16:48   Merge David and Goliath tables efficiently Nicolas Paris
• 22:52   Re: Merge David and Goliath tables efficiently Tomas Vondra

18 June 2023

• 00:42   Re: Merge David and Goliath tables efficiently nicolas paris
• 02:48   Re: Merge David and Goliath tables efficiently Tomas Vondra
• 23:57   Re: Merge David and Goliath tables efficiently nicolas paris

19 June 2023

• 00:23   RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT 
• 10:46   Re: Merge David and Goliath tables efficiently Alvaro Herrera
• 14:34   Re: Merge David and Goliath tables efficiently Tomas Vondra
• 14:53   Re: Merge David and Goliath tables efficiently Tomas Vondra
• 15:09   Re: Merge David and Goliath tables efficiently nicolas paris
• 15:20   Re: Merge David and Goliath tables efficiently nicolas paris
• 16:13   Re: Merge David and Goliath tables efficiently Tomas Vondra
• 18:45   Re: Merge David and Goliath tables efficiently nicolas paris
• 19:30   Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT Benoit Tigeot
• 23:05   Index on (fixed size) bytea value Les
• 23:30   Re: Index on (fixed size) bytea value David G. Johnston

20 June 2023

• 02:25   Re: Merge David and Goliath tables efficiently Tomas Vondra
• 09:13   Re: Index on (fixed size) bytea value Les
• 09:50   Re: Index on (fixed size) bytea value Laurenz Albe
• 10:18   Re: Index on (fixed size) bytea value Les
• 13:02   Re: Merge David and Goliath tables efficiently nicolas paris
• 15:45   Re: Merge David and Goliath tables efficiently Tomas Vondra

25 June 2023

• 09:29   Fwd: Helping planner to chose sequential scan when it improves performance Patrick O'Toole