[postgis-tickets] [PostGIS] #2247: [raster] Create ST_CreateOverviews()
PostGIS
trac at osgeo.org
Thu Sep 11 09:12:25 PDT 2014
#2247: [raster] Create ST_CreateOverviews()
-------------------------------+--------------------------------------------
Reporter: dzwarg | Owner: strk
Type: enhancement | Status: assigned
Priority: medium | Milestone: PostGIS 2.2.0
Component: raster | Version: trunk
Keywords: raster, overviews |
-------------------------------+--------------------------------------------
Comment(by strk):
About the extent parameter of the ST_Retile function: the use case for
specifying one is to use different processes to retile different portions
of the table. Especially useful for big coverages.
If you want a single process you can either find the extent in the
raster_columns view or compute it using st_extent(rast).
Allowing for a null (or omitted) extent could be an added facility, but as
ST_CreateOverview is an easier-to-use wrapper to it already I'm not sure
we need a more user-oriented signature in ST_Retile.
I agree about reducing parameter names (besides, those name are big pain
in general as any name change requires a DROP of the old function...).
About regclass, the advantage is that you get a single value to univoquely
identify a table. There's an implicit cast from 'unknown' (inputted text)
and 'regclass' so you usually just name your table, with or without schema
qualification, and PostgreSQL does the rest for you, making use of the
search_path exactly as done when using normal sql. Very useful. I love
that type. Learning new things is annoying, I know, but once you look it
up, you're going to like it. It's not going anywhere. From a usage point
of view you may consider it just a text representing your table, with
values like 'mytab' or '"MyMixedCaseSchema"."MyMixedCaseTable"'. Maybe the
PostGIS manual could contain a page that talks about this "regclass"
type...
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2247#comment:30>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-tickets
mailing list