Re: weird hash plan cost, starting with pg10

Justin Pryzby <pryzby@telsasoft.com>

From: Justin Pryzby <pryzby@telsasoft.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>, Richard Guo <guofenglinux@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-hackers@lists.postgresql.org

Date: 2020-04-27T16:29:58Z

Lists: pgsql-hackers

On Mon, Apr 27, 2020 at 12:26:03PM -0400, Tom Lane wrote:
> Justin Pryzby <pryzby@telsasoft.com> writes:
> > Checking if you're planning to backpatch this ?
> 
> Are you speaking of 5c27bce7f et al?

Oops, yes, thanks.

I updated wiki/PostgreSQL_13_Open_Items just now.

-- 
Justin

Commits

Make EXPLAIN report maximum hashtable usage across multiple rescans.
- 969f9d0b4ba5 13.0 landed
Clear dangling pointer to avoid bogus EXPLAIN printout in a corner case.
- f3d06e524073 11.8 landed
- 8ffb86644530 12.3 landed
- 5c27bce7f39d 13.0 landed
- 30ce86367e3e 9.5.22 landed
- 242ca479fea1 9.6.18 landed
- 1e6bb6125f33 10.13 landed
psql: Add tab completion for logical replication
- 6f236e1eb8c7 10.0 cited
Make the upper part of the planner work by generating and comparing Paths.
- 3fc6e2d7f5b6 9.6.0 cited