format() changes discussion (was: Re: psql metaqueries with \gexec)

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org>
Subject: format() changes discussion (was: Re: psql metaqueries with \gexec)
Date: 2016-02-22 23:16:03
Message-ID: CADkLM=fmi+koy0Z_skDHF50qZAphGG5m9MwQC5t=_K0sZek94w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> (One thing I had to come up with was processing of arrays, which you
> also see in that example JSON -- it's the specifiers that have a colon
> inside the {}. The part after the colon is used as separator between
> the array elements, and each element is expanded separately.)
>
>
I'm splitting the subject line because it seems like two very different
patches may come out of this.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-02-22 23:24:57 Re: Sanity checking for ./configure options?
Previous Message Alvaro Herrera 2016-02-22 23:13:13 Re: psql metaqueries with \gexec