Files
Dave Page efc0dea335 docs: describe what AI features transmit to LLM providers (#10291)
The AI documentation covered how to configure each provider but said
nothing about what actually leaves the server once one is configured,
which is the first question anyone working under data residency or
procurement constraints will ask.

This adds a provider-neutral section to the AI Reports documentation
setting out what may be transmitted, which is schema definitions,
configuration settings read from pg_settings, query text, EXPLAIN plan
output and, because the Query Tool assistant can run read-only queries,
row data where the assistant judges it necessary; when nothing is
transmitted at all, which is the default, since no provider is
configured out of the box; and the fact that each provider processes
that data under its own terms and in locations of its own choosing, so
the reader knows to check both those terms and their own organisation's
policies before enabling a cloud provider.

It also makes explicit that the list of providers reflects the APIs
pgAdmin can speak to rather than a recommendation, and cross-references
the new section from the AI Assistant notes in the Query Tool
documentation.
2026-08-17 14:25:47 +01:00
..
2016-06-07 09:04:58 +01:00
2019-03-08 15:29:05 +00:00
2024-07-02 10:34:30 +05:30
2026-01-05 13:33:45 +05:30
2026-01-05 13:33:45 +05:30
2019-03-08 15:29:05 +00:00
2019-03-08 15:29:05 +00:00
2019-12-05 06:35:57 -05:00
2020-08-18 11:15:24 +01:00
2021-02-22 16:47:16 +05:30
2022-03-14 15:26:54 +00:00
2022-05-09 12:39:29 +05:30
2022-12-14 15:56:05 +05:30
2023-01-16 19:34:33 +05:30
2023-05-03 15:21:01 +05:30
2023-05-29 11:03:39 +05:30
2023-08-16 15:32:17 +05:30
2023-10-17 15:19:40 +05:30
2024-04-09 08:37:41 +05:30
2024-11-07 22:02:18 +05:30
2025-04-23 15:41:43 +05:30
2025-07-23 17:56:15 +05:30
2023-03-28 22:20:14 +05:30
2019-03-08 15:29:05 +00:00