January 2026 Archives by thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Thu Jan 8 08:20:58 PST 2026
Ending: Fri Jan 30 11:57:37 PST 2026
Messages: 32

• PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Cedric Duprez
  • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Paul Ramsey
    • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Cedric Duprez
    • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Arthur Bazin
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Regina Obe
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Arthur Bazin
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Paul Ramsey
    • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Regina Obe
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Cedric Duprez
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Regina Obe
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Cedric Duprez
      • PostGIS 3.6.1 - ERROR: operator is not unique: public.geometry = public.geometry   Paul Ramsey
• postgis_extensions_upgrade() issue with pg_init_privs   Ari Jolma
• Best ways around memory Error on large st_union for overlay processing   Mike Treglia
  • Best ways around memory Error on large st_union for overlay processing   Paul Ramsey
    • Best ways around memory Error on large st_union for overlay processing   Mike Treglia
      • Best ways around memory Error on large st_union for overlay processing   Paul Ramsey
• Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Bharath Tadikonda
  • Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Greg Troxel
  • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Paul Ramsey
  • RE: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Regina Obe
    • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Bharath Tadikonda
    • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Bharath Tadikonda
      • RE: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Regina Obe
      • Re: Inquiry on planned PostGIS releases and minor-version behavior (now–Feb 28)   Bharath Tadikonda
• St_GeoHash: boundary handling in non-point case   Sztegi
  • St_GeoHash: boundary handling in non-point case   Paul Ramsey
• When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1."   Michael Downey
  • When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1."   Paul Ramsey
    • When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1."   Michael Downey
    • When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1."   Paul Ramsey
      • When did this 'officially' change? "SQL-MM defines the default SRID of all geometry constructors as 0. PostGIS uses a default SRID of -1."   Michael Downey

Last message date: Fri Jan 30 11:57:37 PST 2026
Archived on: Fri Jan 30 12:14:21 PST 2026

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...