Re: New Table Access Methods for Multi and Single Inserts

Jacob Champion <jchampion@timescale.com>

From: Jacob Champion <jchampion@timescale.com>

To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>

Cc: Andres Freund <andres@anarazel.de>, Dilip Kumar <dilipbalaut@gmail.com>, Luc Vlaming <luc@swarm64.com>, Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Paul Guo <guopa@vmware.com>, Jeff Davis <pgsql@j-davis.com>, Michael Paquier <michael@paquier.xyz>, Matthias van de Meent <boekewurm+postgres@gmail.com>

Date: 2023-08-01T17:02:12Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

libpq: Fix some issues in TAP tests for service files
- 2c7bd2ba507e 18.0 cited
Multiple revisions to the GROUP BY reordering tests
- 874d817baa16 17.0 cited
Explore alternative orderings of group-by pathkeys during optimization.
- 0452b461bc40 17.0 cited

On Tue, Aug 1, 2023 at 9:31 AM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
> Thanks. Finally, I  started to spend time on this. Just curious - may
> I know the discussion in/for which this patch is referenced? What was
> the motive? Is it captured somewhere?

It may not have been the only place, but we at least touched on it
during the unconference:

    https://wiki.postgresql.org/wiki/PgCon_2023_Developer_Unconference#Table_AMs

We discussed two related-but-separate ideas:
1) bulk/batch operations and
2) maintenance of TAM state across multiple related operations.

--Jacob