[postgis-tickets] [PostGIS] #3344: Unnecessary use of table/possible speed improvement

[PostGIS]

#3344: Unnecessary use of table/possible speed improvement
--------------------------+---------------------------
  Reporter:  postgispaul  |      Owner:  pramsey
      Type:  enhancement  |     Status:  closed
  Priority:  medium       |  Milestone:  PostGIS 2.1.9
 Component:  postgis      |    Version:  2.1.x
Resolution:  wontfix      |   Keywords:
--------------------------+---------------------------

Comment (by postgispaul):

 Thanks for your thorough answer, and that reassures me that posting in the
 postgis area is correct after all...

 But I still stand by my assumption that being a primary key does in fact
 *not* change the end-result in case of a left-join.

 I assume there isn't a mechanism present where st_extent publishes this
 kind of information (duplicates won't change the result) so that the query
 planner of postgis knows it can skip scanning that table?
 It is not possible for me to make id a primary key, because a polygon can
 have multiple names (different languages).

--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/3344#comment:5>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.