From: | Postgres User <postgres(dot)developer(at)gmail(dot)com> |
---|---|
To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Selecting from table into an array var |
Date: | 2009-12-20 00:08:32 |
Message-ID: | b88c3460912191608v455a11ben816ed033827b65cd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Great call, someone did hose the data. Oddly enough the circular
reference caused no problem when running the stand alone recursive SQL
(with clause).
On Sat, Dec 19, 2009 at 10:41 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> On Sat, Dec 19, 2009 at 1:30 PM, Postgres User
> <postgres(dot)developer(at)gmail(dot)com> wrote:
>>
>> Thanks, your syntax does compile and run.
>>
>> This is where it gets interesting. With your syntax (and variations
>> of it), I'm able to successfully compile and execute. However, as
>> soon as I add a dozen rows to the table, the query failes to complete.
>> It runs until timing out.
>> This prolem does not occur when I remove the SELECT INTO ARRAY
>> statement and simply run the recursive query.
>>
>> Has anyone else seen this behavior?
>
> are you sure you don't have a circular dependency? maybe you have a
> variable/column name clash?
>
> merlin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2009-12-20 00:11:21 | Re: How to use read uncommitted transaction level and set update order |
Previous Message | Andrus | 2009-12-20 00:06:03 | Re: How to use read uncommitted transaction level and set update order |