Re: row literal problem

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: row literal problem
Date: 2012-07-18 20:58:26
Message-ID: CAHyXU0ywPPKEcppvJt+WWRn_rkfm6Wz3r4id-+snvGURRhbfFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 18, 2012 at 3:56 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> hm, it's the 'group by' -- for example if you add group by
> pg_namespace.oid, group by pg_namespace.oid || 'abc', you can invent
> columns that come back into the rowtype.

here's a cut down example:
with q as (select max(v) from (select 1 as v) q group by v) select q from q;

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-07-18 21:17:26 Re: [PERFORM] DELETE vs TRUNCATE explanation
Previous Message Merlin Moncure 2012-07-18 20:56:06 Re: row literal problem