Re: Making aggregate deserialization (and WAL receive) functions slightly faster
От | Amit Kapila |
---|---|
Тема | Re: Making aggregate deserialization (and WAL receive) functions slightly faster |
Дата | |
Msg-id | CAA4eK1KDA=avN-4Dq6KJph+a=GVi6US_BCCZ6Wf1JW9eeZ2hAQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Making aggregate deserialization (and WAL receive) functions slightly faster (David Rowley <dgrowleyml@gmail.com>) |
Ответы |
Re: Making aggregate deserialization (and WAL receive) functions slightly faster
|
Список | pgsql-hackers |
On Tue, Oct 31, 2023 at 2:25 AM David Rowley <dgrowleyml@gmail.com> wrote: > > On Mon, 30 Oct 2023 at 23:48, Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > On Fri, Oct 27, 2023 at 3:23 AM David Rowley <dgrowleyml@gmail.com> wrote: > > > * parallel.c in HandleParallelMessages(): > > > * applyparallelworker.c in HandleParallelApplyMessages(): > > > > Both the above calls are used to handle ERROR/NOTICE messages from > > parallel workers as you have also noticed. The comment atop > > initReadOnlyStringInfo() clearly states that it is used in the > > performance-critical path. So, is it worth changing these places? In > > the future, this may pose the risk of this API being used > > inconsistently. > > I'm ok to leave those ones out. > The other two look good to me. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: