Message-ID: <593b9618c75a20e423e406eaac3a784a1559a142.camel@j-davis.com>
Subject: Re: New Table Access Methods for Multi and Single Inserts
From: Jeff Davis <pgsql@j-davis.com>
To: Luc Vlaming <luc@swarm64.com>, Bharath Rupireddy
	 <bharath.rupireddyforpostgres@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>, PostgreSQL-development
 <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Paul
 Guo <guopa@vmware.com>
Date: Tue, 19 Jan 2021 09:33:09 -0800
In-Reply-To: <2281baee-081c-7360-cb51-4f16e1e91d8c@swarm64.com>
References: 
	<CALj2ACVi9eTRYR=gdca5wxtj3Kk_9q9qVccxsS1hngTGOCjPwQ@mail.gmail.com>
	 <20201217050522.GU30237@telsasoft.com>
	 <CALj2ACVgT1iocd5nQ+rEmqt3xcCONkR037qbc8PiojdR39Ag=w@mail.gmail.com>
	 <20201217204442.GX30237@telsasoft.com>
	 <CALj2ACW3BC5kgdffZ2LD_CT2wQoXVc29kGB74SVWnGZ=UFqcAQ@mail.gmail.com>
	 <20201218175439.GA30237@telsasoft.com>
	 <20201221074725.GF30237@telsasoft.com>
	 <CALj2ACWMnZZCu=G0PJkEeYYicKeuJ-X=SU19i6vQ1+=uXz8u0Q@mail.gmail.com>
	 <20201225023958.GW30237@telsasoft.com>
	 <CALj2ACVDtYYRYD2SC+X2ALOUkhnUcgC7RLxiEYVWW2HxxrfRww@mail.gmail.com>
	 <96eaa813-4ad6-e80a-04a4-cc8082d356dd@swarm64.com>
	 <CALj2ACVsiAZMsP8p5MPg6SSEtoMFFaiAa6j2AFtEQJDhfbgs3Q@mail.gmail.com>
	 <508af801-6356-d36b-1867-011ac6df8f55@swarm64.com>
	 <CALj2ACUmL3+xLFtVbdcNpo_=ubdi=_nsp6MNq__xWwL=NGkdgA@mail.gmail.com>
	 <c54a69a8b60bae42499b86ff771ecbcdad29326d.camel@j-davis.com>
	 <2281baee-081c-7360-cb51-4f16e1e91d8c@swarm64.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 2021-01-18 at 08:58 +0100, Luc Vlaming wrote:
> You mean how it could because of that the table modification API
> uses 
> the table_tuple_insert_speculative ? Just wondering if you think if
> it 
> generally cannot work or would like to see that path / more paths 
> integrated in to the patch.

I think the patch should support INSERT INTO ... SELECT, and it will be
easier to tell if we have the right API when that's integrated.

Regards,
	Jeff Davis