| From: | Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding argument names to aggregate functions |
| Date: | 2023-07-19 17:32:16 |
| Message-ID: | 87zg3rq02n.fsf@wibble.ilmari.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> This patch no longer applied but had a fairly trivial conflict so I've attached
> a rebased v3 addressing the conflict in the hopes of getting this further.
Thanks for the heads-up! Turns out the conflict was due to the new
json(b)_object_agg(_unique)(_strict) functions, which should also have
proargnames added. Here's an updated patch that does that.
- ilmari
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Add-argument-names-to-multi-argument-aggregates.patch | text/x-diff | 4.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-07-19 17:43:11 | Re: harmonize password reuse in vacuumdb, clusterdb, and reindexdb |
| Previous Message | Gurjeet Singh | 2023-07-19 17:28:31 | Re: There should be a way to use the force flag when restoring databases |