Re: a column definition list is required for functions returning "record"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alexander Farber <alexander(dot)farber(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: a column definition list is required for functions returning "record"
Date: 2016-09-07 22:39:26
Message-ID: 2922.1473287966@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> On 9/7/16 2:02 PM, Merlin Moncure wrote:
>> We have that already, it's named 'json_each_text'

> Apparently you haven't looked at json parse/deparse costs ;P

Well, a PL function is gonna be none too cheap either.

Using something like JSON definitely has lots to recommend it --- eg, it
probably won't break when you find out your initial spec for the transport
format was too simplistic.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2016-09-07 22:46:10 Re: How to assemble all fields of (any) view into a string?
Previous Message Jim Nasby 2016-09-07 22:38:37 Re: How to assemble all fields of (any) view into a string?