| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Luc Vlaming <luc(at)swarm64(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Paul Guo <guopa(at)vmware(dot)com> |
| Subject: | Re: New Table Access Methods for Multi and Single Inserts |
| Date: | 2021-01-19 17:33:09 |
| Message-ID: | 593b9618c75a20e423e406eaac3a784a1559a142.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Hilliard | 2021-01-19 17:42:07 | Re: [PATCH 1/1] Fix detection of pwritev support for OSX. |
| Previous Message | Robert Haas | 2021-01-19 17:30:52 | Re: Printing backtrace of postgres processes |