From mat+postgis at tigerdata.com Mon Jan 5 04:34:11 2026 From: mat+postgis at tigerdata.com (Mat Arye) Date: Mon, 5 Jan 2026 13:34:11 +0100 Subject: Collaboration Interest: AI Guidance for PostGIS in pg-aiguide In-Reply-To: References: Message-ID: Hi, Sorry for the delay, but I wanted to close the loop. We now have a PR for a PostGIS skill based on Darafei's excellent work in pg-aiguide: https://github.com/timescale/pg-aiguide/pull/62. (The only changes from the upstream version are the removal of non-PostGIS-specific advice, which we have elsewhere). Thanks again! -Mat On Sun, Nov 30, 2025 at 12:35?AM Darafei "Kom?pa" Praliaskouski < me at komzpa.net> wrote: > Hi, > > I've compiled this list from all my notes, leaving only PostGIS (and a > bit of broader SQL) related things here. > > https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/SKILL.md > > Probably some more will surface once people start using these, > contributions are welcome :) > > On Wed, Nov 26, 2025 at 2:10?PM Mat Arye > wrote: > >> Hey, >> >> This sounds great. If the SKILL.md file is maintained in the postgis >> repository, it would be easy for us to include it in pg-aiguide as well. >> Happy to share our best practices on a call or review/give feedback on a PR >> if any of that would be helpful. >> >> Thanks, >> Mat >> >> On Tue, Nov 25, 2025 at 9:01?PM Darafei "Kom?pa" Praliaskouski < >> me at komzpa.net> wrote: >> >>> Hi, >>> >>> Sounds good. I guess we're at a time when everyone tries to collect >>> their own library for AGENTS.md :) >>> >>> A list of things we put together for Kontur's systems, fixing stuff >>> actually done wrong by LLMs one at a time: >>> https://github.com/konturio/AGENTS.md/blob/main/AGENTS.raw.md >>> >>> What I also learned is that while LLM is randomly forgetful about these >>> spaced repetition helps keep the model's attention on them. >>> For small lists like ours I made a simple trigram based one, >>> >>> https://github.com/konturio/AGENTS.md/blob/main/scripts/spaced_repetition.py >>> >>> LLMs write okay-ish PostGIS SQL. Where they currently totally break is >>> h3, as the library changed all the function names >>> on v3 to v4 migration, and there are subtle name differences across >>> different versions. A skill will be more helpful there. >>> >>> Maybe we can start SKILL.md in postgis repo so that whoever wants to >>> drop it into their AI and generate less-wrong, more-blessed code with >>> typical user error types corrected? >>> We're already building a cheatsheet but some common mistakes can be >>> listed to un-learn them at LLMs. >>> >>> I'll be happy to start and maintain this doc, I'm already doing this >>> anyway for my use cases. >>> >>> >>> On Tue, Nov 25, 2025 at 9:50?PM Mat Arye >>> wrote: >>> >>>> Hi All, >>>> >>>> We've started a new open-source project at Tiger Data aimed at helping >>>> AI agents generate higher-quality Postgres code: >>>> https://github.com/timescale/pg-aiguide >>>> For broader context, here?s the announcement blog describing the >>>> approach and motivations: >>>> >>>> https://www.tigerdata.com/blog/we-taught-ai-to-write-real-postgres-code-open-sourced-it >>>> >>>> As part of this work, we're adding guidance modules for major Postgres >>>> extensions, and PostGIS is at the top of our list. I?m reaching out to ask >>>> whether anyone from the PostGIS community would be interested in >>>> collaborating. >>>> >>>> The core idea is to provide ?skills? that capture best practices, >>>> common pitfalls, and domain-specific patterns so that AI agents can make >>>> better decisions. Here is an example skill: >>>> >>>> https://github.com/timescale/pg-aiguide/blob/main/skills/design-postgres-tables/SKILL.md >>>> >>>> If there?s interest, we?d be happy to set up a call to walk through the >>>> approach and answer questions. >>>> >>>> Beyond skills, the project also includes semantic search over >>>> documentation. We currently index Postgres and TimescaleDB docs, and we >>>> plan to include the PostGIS manual as well. We can handle the processing, >>>> but wanted to check whether there?s anything unusual about the HTML manual >>>> that we should be aware of. We?d also appreciate any guidance on which >>>> versions of the manual are most important to index. >>>> >>>> Thanks for your time, and we?d welcome any feedback or involvement from >>>> the community. >>>> >>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Mon Jan 5 09:05:24 2026 From: lr at pcorp.us (Regina Obe) Date: Mon, 5 Jan 2026 12:05:24 -0500 Subject: PostGIS 2026 Funding Message-ID: <009001dc7e65$7bfd0b50$73f721f0$@pcorp.us> The OSGeo funding budget is due January 15th. https://wiki.osgeo.org/wiki/SAC:Budget#2026 Do we want to ask for funding for anything. I'm thinking any conferences/code sprints that PostGIS development team (PSC and general core team), is planning to attend/manage that is not otherwise covered by company budgets would be good candidates. Any plans for that? Thanks, Regina From pramsey at cleverelephant.ca Wed Jan 7 09:18:45 2026 From: pramsey at cleverelephant.ca (Paul Ramsey) Date: Wed, 7 Jan 2026 09:18:45 -0800 Subject: PostGIS 2026 Funding In-Reply-To: <009001dc7e65$7bfd0b50$73f721f0$@pcorp.us> References: <009001dc7e65$7bfd0b50$73f721f0$@pcorp.us> Message-ID: Having a travel budget in case there is an event we can / need to participate in would be good, even if we don't use it. If we don't, great, more money for OSGeo for next year. On Mon, Jan 5, 2026 at 9:05?AM Regina Obe wrote: > The OSGeo funding budget is due January 15th. > > https://wiki.osgeo.org/wiki/SAC:Budget#2026 > > Do we want to ask for funding for anything. I'm thinking any > conferences/code sprints that PostGIS development team (PSC and general > core > team), is planning to attend/manage that is not otherwise covered by > company > budgets would be good candidates. > > Any plans for that? > > Thanks, > Regina > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lr at pcorp.us Wed Jan 7 09:36:04 2026 From: lr at pcorp.us (Regina Obe) Date: Wed, 7 Jan 2026 12:36:04 -0500 Subject: PostGIS 2026 Funding In-Reply-To: References: <009001dc7e65$7bfd0b50$73f721f0$@pcorp.us> Message-ID: <007301dc7ffc$1962e530$4c28af90$@pcorp.us> Sounds good to me. Oops and sorry I provided the wrong link. https://wiki.osgeo.org/wiki/OSGeo_Budget_2026#OSGeo_Projects I put in $2000 for PostGIS and $2000 for GEOS From: Paul Ramsey Sent: Wednesday, January 7, 2026 12:19 PM To: Regina Obe Cc: PostGIS Development Discussion Subject: Re: PostGIS 2026 Funding Having a travel budget in case there is an event we can / need to participate in would be good, even if we don't use it. If we don't, great, more money for OSGeo for next year. On Mon, Jan 5, 2026 at 9:05?AM Regina Obe > wrote: The OSGeo funding budget is due January 15th. https://wiki.osgeo.org/wiki/SAC:Budget#2026 Do we want to ask for funding for anything. I'm thinking any conferences/code sprints that PostGIS development team (PSC and general core team), is planning to attend/manage that is not otherwise covered by company budgets would be good candidates. Any plans for that? Thanks, Regina -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at komzpa.net Fri Jan 9 03:16:51 2026 From: me at komzpa.net (=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?=) Date: Fri, 9 Jan 2026 15:16:51 +0400 Subject: Collaboration Interest: AI Guidance for PostGIS in pg-aiguide In-Reply-To: References: Message-ID: Hi Mat, I'd prefer you don't strip any lines - many of those aren't "postgis-specific" but are very often created by LLMs around postgis code and usage scenarios. If you think they need to be put elsewhere let's reorganize upstream but not create silent forks where you bundle the file and remove half of it. In other news, there is now an H3 skill file too. https://github.com/postgis/h3-pg/blob/main/docs/SKILL.md On Mon, Jan 5, 2026 at 4:34?PM Mat Arye wrote: > Hi, > > Sorry for the delay, but I wanted to close the loop. We now have a PR for > a PostGIS skill based on Darafei's excellent work in pg-aiguide: > https://github.com/timescale/pg-aiguide/pull/62. (The only changes from > the upstream version are the removal of non-PostGIS-specific advice, which > we have elsewhere). > > Thanks again! > > -Mat > > > On Sun, Nov 30, 2025 at 12:35?AM Darafei "Kom?pa" Praliaskouski < > me at komzpa.net> wrote: > >> Hi, >> >> I've compiled this list from all my notes, leaving only PostGIS (and a >> bit of broader SQL) related things here. >> >> https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/SKILL.md >> >> Probably some more will surface once people start using these, >> contributions are welcome :) >> >> On Wed, Nov 26, 2025 at 2:10?PM Mat Arye >> wrote: >> >>> Hey, >>> >>> This sounds great. If the SKILL.md file is maintained in the postgis >>> repository, it would be easy for us to include it in pg-aiguide as well. >>> Happy to share our best practices on a call or review/give feedback on a PR >>> if any of that would be helpful. >>> >>> Thanks, >>> Mat >>> >>> On Tue, Nov 25, 2025 at 9:01?PM Darafei "Kom?pa" Praliaskouski < >>> me at komzpa.net> wrote: >>> >>>> Hi, >>>> >>>> Sounds good. I guess we're at a time when everyone tries to collect >>>> their own library for AGENTS.md :) >>>> >>>> A list of things we put together for Kontur's systems, fixing stuff >>>> actually done wrong by LLMs one at a time: >>>> https://github.com/konturio/AGENTS.md/blob/main/AGENTS.raw.md >>>> >>>> What I also learned is that while LLM is randomly forgetful about these >>>> spaced repetition helps keep the model's attention on them. >>>> For small lists like ours I made a simple trigram based one, >>>> >>>> https://github.com/konturio/AGENTS.md/blob/main/scripts/spaced_repetition.py >>>> >>>> LLMs write okay-ish PostGIS SQL. Where they currently totally break is >>>> h3, as the library changed all the function names >>>> on v3 to v4 migration, and there are subtle name differences across >>>> different versions. A skill will be more helpful there. >>>> >>>> Maybe we can start SKILL.md in postgis repo so that whoever wants to >>>> drop it into their AI and generate less-wrong, more-blessed code with >>>> typical user error types corrected? >>>> We're already building a cheatsheet but some common mistakes can be >>>> listed to un-learn them at LLMs. >>>> >>>> I'll be happy to start and maintain this doc, I'm already doing this >>>> anyway for my use cases. >>>> >>>> >>>> On Tue, Nov 25, 2025 at 9:50?PM Mat Arye >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> We've started a new open-source project at Tiger Data aimed at helping >>>>> AI agents generate higher-quality Postgres code: >>>>> https://github.com/timescale/pg-aiguide >>>>> For broader context, here?s the announcement blog describing the >>>>> approach and motivations: >>>>> >>>>> https://www.tigerdata.com/blog/we-taught-ai-to-write-real-postgres-code-open-sourced-it >>>>> >>>>> As part of this work, we're adding guidance modules for major Postgres >>>>> extensions, and PostGIS is at the top of our list. I?m reaching out to ask >>>>> whether anyone from the PostGIS community would be interested in >>>>> collaborating. >>>>> >>>>> The core idea is to provide ?skills? that capture best practices, >>>>> common pitfalls, and domain-specific patterns so that AI agents can make >>>>> better decisions. Here is an example skill: >>>>> >>>>> https://github.com/timescale/pg-aiguide/blob/main/skills/design-postgres-tables/SKILL.md >>>>> >>>>> If there?s interest, we?d be happy to set up a call to walk through >>>>> the approach and answer questions. >>>>> >>>>> Beyond skills, the project also includes semantic search over >>>>> documentation. We currently index Postgres and TimescaleDB docs, and we >>>>> plan to include the PostGIS manual as well. We can handle the processing, >>>>> but wanted to check whether there?s anything unusual about the HTML manual >>>>> that we should be aware of. We?d also appreciate any guidance on which >>>>> versions of the manual are most important to index. >>>>> >>>>> Thanks for your time, and we?d welcome any feedback or involvement >>>>> from the community. >>>>> >>>>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From pramsey at cleverelephant.ca Tue Jan 13 12:43:23 2026 From: pramsey at cleverelephant.ca (Paul Ramsey) Date: Tue, 13 Jan 2026 12:43:23 -0800 Subject: ST_DWithin Prepared Message-ID: If you build your own PostGIS and have a workload that uses ST_DWithin, it would be great if you'd try out the development branch (master) and see if your workload is any faster (or slower) after this change. https://github.com/postgis/postgis/commit/48a31d424a91b9fda7c125a5c5594689e87d562c Prepared geometry and caching are not cost free, but hopefully any use cases that degrade only do so a tiny bit, because the ones that get faster get quite a bit faster. P. -------------- next part -------------- An HTML attachment was scrubbed... URL: From strk at kbt.io Thu Jan 15 07:55:23 2026 From: strk at kbt.io (Sandro Santilli) Date: Thu, 15 Jan 2026 16:55:23 +0100 Subject: Motion: Drop support for GEOS < 3.10 in master branch Message-ID: Any GEOS before 3.10 reached end of life: fatture/2026/ricevute/contabili/trim1/20260109-energetic-gas-pietracupa-013805.pdf Current Debian stable (13) ships 3.13 (.0 released on 2024-09-06) What do you think about dropping support for those EOL releases in current master branch of PostGIS, targetting 3.7.0 ? +1 from me --strk; -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: From lr at pcorp.us Thu Jan 15 07:56:39 2026 From: lr at pcorp.us (Regina Obe) Date: Thu, 15 Jan 2026 10:56:39 -0500 Subject: Motion: Drop support for GEOS < 3.10 in master branch In-Reply-To: References: Message-ID: <000701dc8637$893753a0$9ba5fae0$@pcorp.us> > Any GEOS before 3.10 reached end of life: > fatture/2026/ricevute/contabili/trim1/20260109-energetic-gas-pietracupa- > 013805.pdf > > Current Debian stable (13) ships 3.13 (.0 released on 2024-09-06) > > What do you think about dropping support for those EOL releases in current > master branch of PostGIS, targetting 3.7.0 ? > > +1 from me > > --strk; +1 From strk at kbt.io Thu Jan 15 08:16:31 2026 From: strk at kbt.io (Sandro Santilli) Date: Thu, 15 Jan 2026 17:16:31 +0100 Subject: Motion: Drop support for GEOS < 3.10 in master branch In-Reply-To: References: Message-ID: On Thu, Jan 15, 2026 at 04:55:23PM +0100, Sandro Santilli wrote: > > Any GEOS before 3.10 reached end of life: The right link to the GEOS EOL is here: https://libgeos.org/usage/download/ --strk; -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: From pramsey at cleverelephant.ca Thu Jan 15 08:43:27 2026 From: pramsey at cleverelephant.ca (Paul Ramsey) Date: Thu, 15 Jan 2026 08:43:27 -0800 Subject: Motion: Drop support for GEOS < 3.10 in master branch In-Reply-To: <000701dc8637$893753a0$9ba5fae0$@pcorp.us> References: <000701dc8637$893753a0$9ba5fae0$@pcorp.us> Message-ID: +1 > On Jan 15, 2026, at 7:56?AM, Regina Obe wrote: > >> Any GEOS before 3.10 reached end of life: >> fatture/2026/ricevute/contabili/trim1/20260109-energetic-gas-pietracupa- >> 013805.pdf >> >> Current Debian stable (13) ships 3.13 (.0 released on 2024-09-06) >> >> What do you think about dropping support for those EOL releases in current >> master branch of PostGIS, targetting 3.7.0 ? >> >> +1 from me >> >> --strk; > > +1 > From loic.bartoletti at oslandia.com Thu Jan 15 21:09:38 2026 From: loic.bartoletti at oslandia.com (=?utf-8?B?TG/Dr2M=?= BARTOLETTI) Date: Fri, 16 Jan 2026 06:09:38 +0100 Subject: Motion: Drop support for GEOS < 3.10 in master branch In-Reply-To: References: <000701dc8637$893753a0$9ba5fae0$@pcorp.us> Message-ID: +1 On 15/01/2026 08:43, Paul Ramsey wrote: >+1 > >> On Jan 15, 2026, at 7:56?AM, Regina Obe wrote: >> >>> Any GEOS before 3.10 reached end of life: >>> fatture/2026/ricevute/contabili/trim1/20260109-energetic-gas-pietracupa- >>> 013805.pdf >>> >>> Current Debian stable (13) ships 3.13 (.0 released on 2024-09-06) >>> >>> What do you think about dropping support for those EOL releases in current >>> master branch of PostGIS, targetting 3.7.0 ? >>> >>> +1 from me >>> >>> --strk; >> >> +1 >> >