Re: Parallelized polymorphic aggs, and aggtype vs aggoutputtype
От | David Rowley |
---|---|
Тема | Re: Parallelized polymorphic aggs, and aggtype vs aggoutputtype |
Дата | |
Msg-id | CAKJS1f-4=nO+nZoGC8RKsCj8gjwrmpXVKNVPrUidQK75M-V+0w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallelized polymorphic aggs, and aggtype vs aggoutputtype (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 23 June 2016 at 08:53, Tom Lane <tgl@sss.pgh.pa.us> wrote: > I wrote: >> David Rowley <david.rowley@2ndquadrant.com> writes: >>> I've gone and implemented the dummy argument approach for >>> deserialization functions. > >> How do you feel about the further idea of locking down the signatures >> to be exactly "serialize(internal) returns bytea" and "deserialize(bytea, >> internal) returns internal", and removing pg_aggregate.aggserialtype? >> I don't see very much value in allowing any other nominal transmission >> type besides bytea; and the less flexibility in these function signatures, >> the less chance of confusion/misuse of other internal-related functions. I don't object to removing it. If we find a use for non-bytea serial types down the line, then we can add it again. > Not hearing any objections, pushed that way. Many thanks for committing those fixes. -- David Rowley http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: