From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | AlexK <alkuzo(at)gmail(dot)com> |
Cc: | postgres list <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: How to unnest an array with element indexes |
Date: | 2014-02-20 04:17:05 |
Message-ID: | CAFj8pRBB90SYpxWY-sLxciODHD-NoPV=uRJch-qmNFxcSLi+2w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
2014-02-19 21:55 GMT+01:00 AlexK <alkuzo(at)gmail(dot)com>:
> Pavel,
>
> This works for me, thank you!
>
> Presumably foreach is guaranteed to iterate array elements in order: "The
> elements are visited in storage order, regardless of the number of array
> dimensions", quoted from this:
>
> http://www.postgresql.org/docs/9.2/static/plpgsql-control-structures.html
>
> Since parallelism is coming up, will this behavior stay as documented? My
> arrays are as big as 20K-30K elements, maybe more.
>
I cannot to say, what will be in next years - but it is less probable --
plans for parallelism are related for SQL executor internals - like
parallel sort - or parallel hashing.
we have no plans do plpgsql parallel - now works well - and it is relative
simple to maintain it.
Regards
Pavel
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/How-to-unnest-an-array-with-element-indexes-tp5792770p5792787.html
> Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>
From | Date | Subject | |
---|---|---|---|
Next Message | Kumar Babu P G | 2014-02-24 06:37:24 | Postgres behavior - Conditional statements |
Previous Message | bricklen | 2014-02-19 23:25:49 | Re: Selecting consecutive dates as integers in yyyymmdd format |