Re: Performance degradation on concurrent COPY into a single relation in PG16.
От | David Rowley |
---|---|
Тема | Re: Performance degradation on concurrent COPY into a single relation in PG16. |
Дата | |
Msg-id | CAApHDvquQG354U9evKr1sBetDE+O5Ytgt2UmTKQYwg0rEuO80Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Performance degradation on concurrent COPY into a single relation in PG16. (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Performance degradation on concurrent COPY into a single relation in PG16.
|
Список | pgsql-hackers |
On Wed, 26 Jul 2023 at 03:50, Andres Freund <andres@anarazel.de> wrote: > On 2023-07-25 23:37:08 +1200, David Rowley wrote: > > On Tue, 25 Jul 2023 at 17:34, Andres Freund <andres@anarazel.de> wrote: > > I've not really studied the fix_COPY_DEFAULT.patch patch. Is there a > > reason to delay committing that? It would be good to eliminate that > > as a variable for the current performance regression. > > Yea, I don't think there's a reason to hold off on that. Sawada-san, do you > want to commit it? Or Andrew? Just to keep this moving and to make it easier for people to test the pg_strtoint patches, I've pushed the fix_COPY_DEFAULT.patch patch. The only thing I changed was to move the line that was allocating the array to a location more aligned with the order that the fields are defined in the struct. David
В списке pgsql-hackers по дате отправления: