[postgis-devel] GUC, anyone ?

[Paul Ramsey]

Right, my favourite GUC was output precision. It's a hard call, since
anything which is a GUC could also be a function parameter instead...
so there's a philosophy to it.

P.

On Wed, Dec 21, 2011 at 6:11 AM, Sandro Santilli <strk at keybit.net> wrote:
> So I've spent some time inspecting GUC, which would be a nice
> thing to have in PostGIS. GUC is about doing things like:
>
>  SET postgis.out.gml.default_prefix TO "gml"
>  SET postgis.geos.exception_policy TO "null"
>  SET postgis.overlay.snap_tolerance TO 0.234
>
> Things like that.
>
> It is likely too late for 2.0 but I thought to mention it
> now as it's not really anything new. I've found a few tickets
> calling for it and created a new one to serve as a general one:
>
>  http://trac.osgeo.org/postgis/ticket/1393
>
> It seems to me that the most time consuming part would be
> defining what configurations we want, and started a wiki
> page about that:
>
>  http://trac.osgeo.org/postgis/wiki/DevGUC
>
> I invite anyone with "a need for config" to write down her own
> directive with a description of what it should or shouldn't do.
>
> There are a few lines for GUC handling in the new
> postgis/postgis_module.c file. They are if-0'ed out but can
> serve as a quick way to test the calls against multiple
> PostgreSQL versions. I only tested against 8.4.
>
> --strk;
>
>  ,------o-.
>  |   __/  |    Thank you for PostGIS-2.0 Topology !
>  |  / 2.0 |    http://www.pledgebank.com/postgistopology
>  `-o------'
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel