[postgis-devel] Proj GUCs

[Regina Obe]

As I recall it was mostly an issue when we had minor version in our lib file.  Doing an upgrade would force a reload of the same named GUC by the new library. Even then it was mostly an issue with the backend guc which we got rid of in 3.0

 

I haven’t had issues recently with using the other gucs.

I don’t think I’ve even gotten the annoying message of postgis.gdal_enabled_drivers or gdalpath I used to get in the pre-3.0 days.

 

I use mostly postgis.gdal_enabled_drivers guc.

 

 

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Tuesday, June 20, 2023 4:26 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Proj GUCs

 

 





On Jun 20, 2023, at 12:45 PM, Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca> > wrote:

 

So, looking for some feedback and institutional memory here.

 

One important piece of institutional memory is around: remember when we had upgrade problems because of GUC variables? Anyone remember what it was that was triggering that? Are we in danger if we introduce GUCs…?

 

P

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20230620/e01f2f60/attachment.htm>