Changes between Initial Version and Version 1 of Ticket #4271, comment 3


Ignore:
Timestamp:
Dec 10, 2018, 12:12:00 PM (6 years ago)
Author:
robe

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4271, comment 3

    initial v1  
    33We have the next for production versions too and it works.  In the case of people pg_upgrading from same PostGIS version older PostgreSQL to same PostGIS version to newer PostgreSQL, this is going to be a pretty common occurrence.  Let's not confuse them further by telling them they need to do "force".
    44
    5 IT's too late to introduce a force in PostGIS 2.5 since we can't make API changes.  We COULD have a force in PostGIS 3.0.  Though I'm thinking under what circumstances would I need a force (aside from the dev case and the "When I'm upping my PostgreSQL game, but not my PostGIS game"
     5IT's too late to introduce a force in PostGIS 2.5 anyway since we can't make API changes.  We COULD have a force in PostGIS 3.0.  Though I'm thinking under what circumstances would I need a force (aside from the dev case and the "When I'm upping my PostgreSQL game, but not my PostGIS game"