From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Function for dealing with xlog data |
Date: | 2010-12-28 13:57:46 |
Message-ID: | 1293544622-sup-8367@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Magnus Hagander's message of mar dic 28 10:46:31 -0300 2010:
> On Tue, Dec 28, 2010 at 14:39, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> >> What's the best way of doing it? Should we have a function that takes
> >> text as input, or should the functions in question be made to return a
> >> new datatype that could then be casted?
> >
> > The new datatype seems more elegant, but a conversion function would
> > be a lot less work.
>
> Well, yeah, that was obvious ;) The question is, how much do we prefer
> the more elegant method? ;)
If we go the new type route, do we need it to have an implicit cast to
text, for backwards compatibility?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2010-12-28 14:08:36 | Re: "writable CTEs" |
Previous Message | Magnus Hagander | 2010-12-28 13:46:31 | Re: Function for dealing with xlog data |