Re: should INSERT SELECT use a BulkInsertState? - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: should INSERT SELECT use a BulkInsertState?
Date
Msg-id 20200510155818.GA10164@telsasoft.com
Whole thread Raw
In response to should INSERT SELECT use a BulkInsertState?  (Justin Pryzby <pryzby@telsasoft.com>)
List 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

pgsql-hackers by date:

Previous
From: otar shavadze
Date:
Subject: Re: Cast json array to postgres array and preserve order of elements
Next
From: Alexander Lakhin
Date:
Subject: gcov coverage data not full with immediate stop