[SCM] PostGIS branch master updated. 3.7.0beta1-132-g7733d37ea0
git at osgeo.org
git at osgeo.org
Wed Jul 29 11:44:40 PDT 2026
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".
The branch, master has been updated
via 7733d37ea04f187c318cff0e6e2f95e1dab7a92a (commit)
via 043885ba34311b6378c0fc34526f76a241d26bdc (commit)
from b0acf1ca83d9e5cae016dd69ed6dbbca48c3a7a2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 7733d37ea04f187c318cff0e6e2f95e1dab7a92a
Merge: b0acf1ca83 043885ba34
Author: Darafei Praliaskouski <komzpa at gmail.com>
Date: Wed Jul 29 11:44:29 2026 -0700
Merge pull request 'Move maintained Trac wiki notes into developer docs' (!625) from Komzpa/postgis:ai/trac-wiki-doc-migration-20260729 into master
Fold maintained Trac wiki guidance into the repository developer docs.
This moves durable development workflow notes out of Trac-only pages and into
the maintained documentation tree:
* Docker development container host-connectivity notes from `DevWikiDockerTesting`
* new SQL feature documentation checklist details from `DevWikiDocNewFeature`
* practical regression-test troubleshooting from `UsersWikiMakeCheckConsiderations`
* current documentation, source-code, package, and Windows-install links in the
manual and documentation README
The old `doc/trac-wiki/` pointer in `doc/README` is also removed because that
directory is not present in the current tree.
Validation:
* `git diff --check`
* `xmllint --noout doc/postgis.xml`
* checked that touched current-doc entry points no longer contain live
`trac.osgeo.org/postgis/wiki` links, except historical provenance notes
Reviewed-on: https://gitea.osgeo.org/postgis/postgis/pulls/625
commit 043885ba34311b6378c0fc34526f76a241d26bdc
Author: Darafei Praliaskouski <me at komzpa.net>
Date: Wed Jul 29 22:38:25 2026 +0400
Move maintained Trac wiki notes into developer docs
diff --git a/doc/README b/doc/README
index 84f183d6a1..dc0e308c19 100644
--- a/doc/README
+++ b/doc/README
@@ -61,8 +61,8 @@ manual at https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/developm
for layout roles, labels, textual-output policy, native geometry/EWKT output
handling, and the visual review procedure.
-To run garden tests against functions, follow these instructions on the PostGIS
-dev wiki: http://trac.osgeo.org/postgis/wiki/DevWikiGardenTest
+To run garden tests against functions, see the Garden Checks section in
+https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/development/testing/.
Manual example tests are opt-out. A parseable SQL ``programlisting`` with
expected output is tested by default. Add ``role="requires-external-state"`` when
@@ -155,5 +155,6 @@ features used elsewhere in the manual.
For contributor workflow, local testing, and garden checks, see
https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/development/.
-The audited Trac wiki migration record and recovered attachments live in
-``doc/trac-wiki/``.
+Historical Trac wiki material that is still maintained has been folded into the
+developer documentation under ``doc/development/``, the user manual, or the
+public website.
diff --git a/doc/administration.xml b/doc/administration.xml
index 20d4dcc416..a99ec44a60 100644
--- a/doc/administration.xml
+++ b/doc/administration.xml
@@ -223,7 +223,8 @@ string, and next time you'll need to drop the "next" suffix again:
symbol errors or bringing forward deprecated objects.
</para>
- <para>Supplementary instructions for windows users are available at <link xlink:href="http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade">Windows Hard upgrade</link>.</para>
+ <para>Supplementary instructions for windows users are available in the
+ <link xlink:href="https://postgis.net/documentation/getting_started/install_windows/">PostGIS Windows installation guide</link>.</para>
<para>
diff --git a/doc/development/contributing.md b/doc/development/contributing.md
index 58c265251a..89125da020 100644
--- a/doc/development/contributing.md
+++ b/doc/development/contributing.md
@@ -100,7 +100,9 @@ Patch submission basics:
* Follow [Coding style](style.md) for C naming, formatting, and Doxygen
comments before writing or submitting source patches.
* Add documentation in the same change when a feature adds or changes SQL
- user-visible behavior.
+ user-visible behavior. New SQL functions must follow the
+ [manual documentation workflow](manual.md#documenting-new-sql-features),
+ including `Availability:` notes and generated SQL comments.
* For SQL API, upgrade, and release-policy changes, read
[Release and upgrade rules](release/_index.md) before opening a pull request.
* Git patches sent by email are also accepted; see
diff --git a/doc/development/environment/docker.md b/doc/development/environment/docker.md
index ebbc046baa..6ee062e521 100644
--- a/doc/development/environment/docker.md
+++ b/doc/development/environment/docker.md
@@ -49,6 +49,30 @@ make -j"$(nproc)"
make check
```
+For interactive debugging, keep the container alive and enter it with:
+
+```sh
+docker exec -it postgis-dev /bin/bash
+pg_lsclusters
+```
+
+`pg_lsclusters` shows which PostgreSQL major uses each port inside the
+container. To connect from the host, expose the matching port in `docker run`,
+allow PostgreSQL to listen beyond the container loopback interface, and reload
+the cluster:
+
+```sh
+export PGVER=15
+export PGPORT="$(grep ^port /etc/postgresql/${PGVER}/main/postgresql.conf | awk '{print $3}')"
+psql -d postgres -c "ALTER SYSTEM SET listen_addresses='*';"
+printf '%s\n' "host all all 0.0.0.0/0 scram-sha-256" >> "/etc/postgresql/${PGVER}/main/pg_hba.conf"
+psql -d postgres -c "ALTER ROLE postgres PASSWORD 'change-me';"
+service postgresql restart "${PGVER}"
+```
+
+Use a stronger password and narrower `pg_hba.conf` rule on shared hosts. The
+example is intended for a short-lived local development container.
+
From the host, connect to the PostgreSQL version whose container port you
exposed. For example, if PostgreSQL inside the container listens on `5436` and
the host port mapping is `6436:5436`, use:
diff --git a/doc/development/manual.md b/doc/development/manual.md
index dc902d667a..3249af9f43 100644
--- a/doc/development/manual.md
+++ b/doc/development/manual.md
@@ -111,6 +111,21 @@ For a new function:
one self-contained query and let the visual-example manifest supply the
figure to HTML and PDF.
+Before submitting the patch, verify that the documentation feeds every public
+surface generated from it:
+
+```sh
+make -C doc comments
+make -C doc html
+```
+
+The comments target regenerates `postgis_comments.sql`,
+`raster_comments.sql`, `topology_comments.sql`, and `sfcgal_comments.sql` from
+the reference text. These comments are what users see through database clients
+such as psql, pgAdmin, and other tools that display PostgreSQL object comments,
+so the `refpurpose`, signatures, and examples should make sense outside the
+HTML manual too.
+
Run `make -C regress visual-examples` before building HTML or PDF. It verifies
every runnable example and automatically generates a figure for geometry found
in the result or in SQL literals. The staged PostGIS library supplies the SVG
diff --git a/doc/development/testing/_index.md b/doc/development/testing/_index.md
index 47c9a8becf..506c9da840 100644
--- a/doc/development/testing/_index.md
+++ b/doc/development/testing/_index.md
@@ -57,6 +57,29 @@ When testing against several PostgreSQL installs, put the target PostgreSQL
client binaries first in `PATH` and set `PGPORT`, `PGUSER`, and `PGHOST`
explicitly.
+If the harness connects to the wrong cluster, inspect the active PostgreSQL
+binary and connection settings before changing the test:
+
+```sh
+which pg_config
+pg_config --version
+env | grep '^PG'
+```
+
+The test cluster must allow the selected user to connect locally and create the
+temporary regression database. A local throw-away test cluster often uses a
+topmost `pg_hba.conf` rule such as:
+
+```text
+host all all 127.0.0.1/32 trust
+```
+
+Use a narrower or password-based rule on shared machines, then reload the
+cluster before rerunning the tests. On Windows or mixed checkout environments,
+unexpected diffs in otherwise unchanged `_expected` files can come from line
+endings; normalize the affected regression files before treating the output as
+a behavior change.
+
### Sandboxed Regression Roles
Continuous integration workers are frequently configured with sandboxed
diff --git a/doc/installation.xml b/doc/installation.xml
index 3e1a01d894..cc5526ac45 100644
--- a/doc/installation.xml
+++ b/doc/installation.xml
@@ -33,9 +33,10 @@ in each individual database you want to use it in.
In many cases compilation is only necessary if you want the most
bleeding edge versions or you are a package maintainer.
</para>
- <para>This section includes general compilation instructions, if you are compiling for Windows etc
- or another OS, you may find additional more detailed help at <link xlink:href="https://trac.osgeo.org/postgis/wiki/UsersWikiInstall">PostGIS User contributed compile guides</link> and <link xlink:href="http://trac.osgeo.org/postgis/wiki/DevWikiMain">PostGIS Dev Wiki</link>.</para>
- <para>Pre-Built Packages for various OS are listed in <link xlink:href="https://trac.osgeo.org/postgis/wiki/UsersWikiPackages">PostGIS Pre-built Packages</link></para>
+ <para>This section includes general compilation instructions. If you are compiling for Windows
+ or another operating system, see the <link xlink:href="https://postgis.net/documentation/getting_started/">PostGIS getting started guides</link>
+ and the <link xlink:href="https://gitea.osgeo.org/postgis/postgis/src/branch/master/doc/development/environment/">development environment guides</link>.</para>
+ <para>Pre-Built Packages for various OS are listed in the <link xlink:href="https://postgis.net/documentation/getting_started/">PostGIS getting started guides</link></para>
<para>If you are a windows user, you can get stable builds via Stackbuilder or <link xlink:href="https://postgis.net/windows_downloads">PostGIS Windows download site</link>
We also have <link xlink:href="https://postgis.net/windows_downloads">very bleeding-edge windows experimental builds</link> that are built usually once or twice a week or whenever anything exciting happens. You can
use these to experiment with the in progress releases of PostGIS</para>
@@ -525,7 +526,7 @@ sh autogen.sh
<note>
<para>
If you obtained PostGIS from the
- <link xlink:href="https://trac.osgeo.org/postgis/wiki/CodeRepository">
+ <link xlink:href="https://postgis.net/development/source_code/">
code repository
</link>
, the first step is really to run the script
-----------------------------------------------------------------------
Summary of changes:
doc/README | 9 +++++----
doc/administration.xml | 3 ++-
doc/development/contributing.md | 4 +++-
doc/development/environment/docker.md | 24 ++++++++++++++++++++++++
doc/development/manual.md | 15 +++++++++++++++
doc/development/testing/_index.md | 23 +++++++++++++++++++++++
doc/installation.xml | 9 +++++----
7 files changed, 77 insertions(+), 10 deletions(-)
hooks/post-receive
--
PostGIS
More information about the postgis-tickets
mailing list