Changes between Version 1 and Version 2 of Ticket #3344, comment 5


Ignore:
Timestamp:
10/24/15 08:10:28 (9 years ago)
Author:
postgispaul

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3344, comment 5

    v1 v2  
    33But 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.
    44
    5 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?
     5I 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 postgres knows it can skip scanning that table?
    66It is not possible for me to make id a primary key, because a polygon can have multiple names (different languages).
    77