On 9 January 2014 15:33, Tom Lane wrote:
> Robert Haas writes:
>> On Tue, Jan 7, 2014 at 1:15 PM, Tom Lane wrote:
>>> The next question is if we should allow it with LATERAL. That would
>>> essentially be treating "subscriber" as having implicitly appeared at the
>>> start of the FROM list, whi
Robert Haas writes:
> On Tue, Jan 7, 2014 at 1:15 PM, Tom Lane wrote:
>> The next question is if we should allow it with LATERAL. That would
>> essentially be treating "subscriber" as having implicitly appeared at the
>> start of the FROM list, which I guess is all right ... but does anyone
>> w
On Tue, Jan 7, 2014 at 1:15 PM, Tom Lane wrote:
> Emre Hasegeli writes:
>> I get assertion failure on initsplan.c line 1325 while executing following
>> query
>> on HEAD (edc43458d797a5956f4bf39af18cf62abb0077db). It works fine
>> without --enable-cassert.
>
>> update subscriber set properties =
Emre Hasegeli writes:
> I get assertion failure on initsplan.c line 1325 while executing following
> query
> on HEAD (edc43458d797a5956f4bf39af18cf62abb0077db). It works fine
> without --enable-cassert.
> update subscriber set properties = hstore(a) from (select firstname,
> lastname from player
I get assertion failure on initsplan.c line 1325 while executing following query
on HEAD (edc43458d797a5956f4bf39af18cf62abb0077db). It works fine
without --enable-cassert.
update subscriber set properties = hstore(a) from (select firstname,
lastname from player where player.id = subscriber.id) as
