From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | Liang Shen <shenzhuxi(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: ST_Union(rast, uniontype) treat bands with different classes as the same as first band |
Date: | 2023-01-20 14:42:10 |
Message-ID: | Y8qoQiK3Hi3ZGOzq@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Jan 20, 2023 at 01:56:51PM +0000, Liang Shen wrote:
> Related to https://trac.osgeo.org/postgis/ticket/2200 support multiple
> bands issue
>
> If the $RASTER has bands like ARRAY['8BUI', '16BUI'], the result of
> ```
> ST_Union(
> $RASTER,
> ARRAY[
> ROW(1, 'SUM'),
> ROW(2, 'MAX')
> ]::unionarg[]
> )
> ```
> will be like ARRAY['8BUI', ' 8BUI'].
>
> ST_Union always uses the first band class to process the 2nd band and
> ignore the original class.
You might want to report this bug to postgis devs, as it's clearly not
postgresql bug.
Their page (https://postgis.net/support/) lists
https://trac.osgeo.org/postgis as their bug tracker.
depesz
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-01-20 15:42:10 | Re: BUG #17756: Invalid replica indentity set order in a dump |
Previous Message | Liang Shen | 2023-01-20 13:56:51 | ST_Union(rast, uniontype) treat bands with different classes as the same as first band |