| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: should INSERT SELECT use a BulkInsertState? |
| Date: | 2020-05-10 15:58:18 |
| Message-ID: | 20200510155818.GA10164@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 08, 2020 at 02:25:45AM -0500, Justin Pryzby wrote:
> Seems to me it should, at least conditionally. At least if there's a function
> scan or a relation or ..
>
> I mentioned a bit about our use-case here:
> https://www.postgresql.org/message-id/20200219173742.GA30939%40telsasoft.com
> => I'd prefer our loaders to write their own data rather than dirtying large
> fractions of buffer cache and leaving it around for other backends to clean up.
Nobody suggested otherwise so I added here and cleaned up to pass tests.
https://commitfest.postgresql.org/28/2553/
--
Justin
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Make-INSERT-SELECT-use-a-BulkInsertState.patch | text/x-diff | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lakhin | 2020-05-10 16:00:00 | gcov coverage data not full with immediate stop |
| Previous Message | otar shavadze | 2020-05-10 15:56:47 | Re: Cast json array to postgres array and preserve order of elements |