| From: | Wolfgang Walther <walther(at)technowledgy(dot)de> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Docs: Order of json aggregate functions |
| Date: | 2024-06-19 17:49:53 |
| Message-ID: | 6a7b910c-3feb-4006-b817-9b4759cb6bb6@technowledgy.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The order of json related aggregate functions in the docs is currently
like this:
[...]
json_agg
json_objectagg
json_object_agg
json_object_agg_strict
json_object_agg_unique
json_arrayagg
json_object_agg_unique_strict
max
min
range_agg
range_intersect_agg
json_agg_strict
[...]
json_arrayagg and json_agg_strict are out of place.
Attached patch puts them in the right spot. This is the same down to v16.
Best,
Wolfgang
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fix-order-of-json-aggregate-functions-in-docs.patch | text/x-patch | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-06-19 17:50:09 | Re: Extension security improvement: Add support for extensions with an owned schema |
| Previous Message | Alvaro Herrera | 2024-06-19 17:39:42 | Re: Maybe don't process multi xmax in FreezeMultiXactId() if it is already marked as invalid? |