From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, khuddleston(at)pivotal(dot)io |
Subject: | Re: Making "COPY partitioned_table FROM" faster |
Date: | 2018-07-28 17:24:08 |
Message-ID: | CAAKRu_bgm47oaRyGuG4-=jhJWBYvx==4VoW=7jH0wf1-jWa7DQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 26, 2018 at 7:26 PM, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:
> Fixed in the attached v4. That's the only change.
>
I don't see an attachment.
> So, I thinking I'm missing something. Which of the changes would cause the
> > performance improvement from patch v2 to v3? My understanding is:
>
> You could probably narrow it down by reverting those changed
> one-by-one and seeing if it was just one in particular that caused the
> performance improvement or if it was some combination of the changed.
> Sounds like that would take quite a bit of time and it would only be
> for a learning experience, but an interesting one!
We are probably okay without doing that in this case. Assuming v4 changed
that typo, I feel ready to change the status of the patch to "ready for
committer".
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-07-28 17:52:12 | Re: Segfault logical replication PG 10.4 |
Previous Message | Phil Florent | 2018-07-28 16:46:02 | RE: [Proposal] Add accumulated statistics for wait event |