Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns |
Дата | |
Msg-id | CAB7nPqQ-K8m1UC3J00MPHFZN5oK5Hw1_EVhSyWztHmY974OJ+w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with a lot of columns (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: [HACKERS] SendRowDescriptionMessage() is slow for queries with alot of columns
|
Список | pgsql-hackers |
On Thu, Sep 28, 2017 at 1:31 PM, Andres Freund <andres@anarazel.de> wrote: > On September 27, 2017 9:06:49 PM PDT, Andres Freund <andres@anarazel.de> wrote: >>On 2017-09-28 00:01:53 -0400, Tom Lane wrote: >>> Could we please not perpetuate the brain-dead "s" and "l" suffixes >>> on these names? Given the lack of standardization as to how long >>> "long" is, that's entirely unhelpful. I'd be fine with names like >>> pg_ntoh16/32/64 and pg_hton16/32/64. >> >>Yes. I'd polled a few people and they leaned towards those. But I'm >>perfectly happy to do that renaming. > > If somebody wants to argue for replacing hton/ntoh with {to,from}big or *be, now's the time. OK. pg_hton16/32/64 and pg_ntoh16/32/64 are fine enough IMO. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: