Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)
Date
Msg-id CAB7nPqTAuKRd1GhjRVFdOtfG_CRz0M4c6L90vOMTcMnFY1NEqQ@mail.gmail.com
Whole thread Raw
In response to Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)  (Marko Tiikkaja <marko@joh.to>)
Responses Re: COPY (INSERT/UPDATE/DELETE .. RETURNING ..)  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
On Sun, Nov 22, 2015 at 9:54 AM, Marko Tiikkaja wrote:
> Attached the test case I used; removing a batch of old rows from a table
> through an index.  Best out of three runs, I get 13.1 seconds versus 15.0
> seconds, which should amount to an improvement of around 12.7%.

Thanks for the test case. I haven't seen that much, up to 5% on my
laptop still that's not bad thinking that it saves one execution step.

> Also attached a v3 of the patch which adds an Assert on top of the test case
> changes suggested by you.

Sorry for the late reply. I have been playing a bit more with this
patch and I am withdrawing my comments regarding the use of SelectStmt
here. I have looked at the patch again, noticing typos as well as
comments not updated, particularly for psql's \copy, resulting in the
attached.

Patch is switched to "ready for committer".
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: Making tab-complete.c easier to maintain
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP