Re: Parallel INSERT (INTO ... SELECT ...) - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Parallel INSERT (INTO ... SELECT ...)
Date
Msg-id CA+hUKG+JK=tfN3=rS2wvqwQiCSqqT1fjhk6P1_F5+aKoi=b0KQ@mail.gmail.com
Whole thread Raw
In response to Re: Parallel INSERT (INTO ... SELECT ...)  (Greg Nancarrow <gregn4422@gmail.com>)
List pgsql-hackers
On Mon, Oct 12, 2020 at 6:35 PM Greg Nancarrow <gregn4422@gmail.com> wrote:
> On Mon, Oct 12, 2020 at 2:11 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> > Yeah, I think we should go ahead and fix that up front.  Here's a
> > version with a commit message.
>
> I've checked it and tested it, and it looks fine to me.
> Also, it seems to align with the gripe in the old comment about width
> ("XXX this is totally wrong: we should report zero if no RETURNING
> ...").
> I'm happy for you to commit it.

Pushed, though I left most of that comment there because the width
estimate still needs work when you do use RETURNING.  At least we now
have rows=0 for queries without RETURNING, which was a bigger problem
for your patch.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: speed up unicode normalization quick check
Next
From: "Hou, Zhijie"
Date:
Subject: RE: Remove some unnecessary if-condition