Opened 4 years ago

Last modified 3 months ago

#4822 new defect

Set costs and parallel settings on tiger functions

Reported by: robe Owned by: robe
Priority: medium Milestone: PostGIS 3.6.0
Component: tiger geocoder Version: 3.1.x
Keywords: Cc:

Description (last modified by robe)

Now that 9.6 is the minimum I can set costs and parallel settings.

I discovered one of my geocodings was slower in PostgreSQL 12 because the geocoding process was repeating for each because the CTE is not always materialized now. Setting costs high setting expected rows returned from default 1000 to 1 alleviates that.

In fact the ROWS count seemed to have a much greater impact than anything else.

Change History (12)

comment:1 by robe, 4 years ago

Version: 3.0.x3.1.x

comment:2 by robe, 4 years ago

Description: modified (diff)

comment:3 by Regina Obe <lr@…>, 4 years ago

In a3c1c63/git:

Set row estimate to 1 and mark as parallel safe the geocode function. References #4822 for PostGIS 3.2 (master)

comment:4 by pramsey, 4 years ago

Milestone: PostGIS 3.1.1PostGIS 3.1.2

comment:5 by pramsey, 4 years ago

Milestone: PostGIS 3.1.23.1.3

comment:6 by pramsey, 4 years ago

Milestone: 3.1.3PostGIS 3.1.3

Milestone renamed

comment:7 by robe, 3 years ago

Milestone: PostGIS 3.1.3PostGIS 3.1.4

In prep for 3.1.3 release

comment:8 by robe, 3 years ago

Milestone: PostGIS 3.1.4PostGIS 3.2.0

comment:9 by robe, 3 years ago

Milestone: PostGIS 3.2.0PostGIS 3.3.0

comment:10 by robe, 2 years ago

Milestone: PostGIS 3.3.0PostGIS 3.4.0

comment:11 by robe, 18 months ago

Milestone: PostGIS 3.4.0PostGIS 3.5.0

comment:12 by robe, 3 months ago

Milestone: PostGIS 3.5.0PostGIS 3.6.0
Note: See TracTickets for help on using tickets.