Re: Function for dealing with xlog data - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Function for dealing with xlog data
Date
Msg-id 1293544622-sup-8367@alvh.no-ip.org
Whole thread Raw
In response to Re: Function for dealing with xlog data  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Function for dealing with xlog data  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@gmail.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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Function for dealing with xlog data
Next
From: Peter Geoghegan
Date:
Subject: Re: "writable CTEs"