Re: proposal: set GUC variables for single query

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Urbański <wulczer(at)wulczer(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: set GUC variables for single query
Date: 2011-10-17 14:11:39
Message-ID: 12962.1318860699@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

=?UTF-8?B?SmFuIFVyYmHFhHNraQ==?= <wulczer(at)wulczer(dot)org> writes:
> On 17/10/11 02:53, Robert Haas wrote:
>> I previously floated the idea of using a new keyword, possibly LET,
>> for this, like this:
>>
>> LET var = value [, ...] IN query

> LET was something I thought about, although you'd have to use something
> like parenthesis around the GUC assignements because "value" can contain
> commas, leading to shift/reduce conflicts (that sucks, unfortunately).

Probably better to forbid commas --- people can always put such values
inside a quoted literal.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-10-17 15:37:56 Re: Underspecified window queries in regression tests
Previous Message Erik Rijkers 2011-10-17 14:07:23 Re: Range Types - typo + NULL string constructor