[postgis-devel] [PostGIS] #2122: [raster] Real extent feature lost after metadata as views

Sandro Santilli strk at keybit.net
Fri Nov 30 08:51:59 PST 2012

On Fri, Nov 30, 2012 at 08:43:36AM -0800, Bborie Park wrote:
> On Fri, Nov 30, 2012 at 8:34 AM, Mateusz Loskot <mateusz at loskot.net> wrote:

> > If it is possible, then storing the two hard-coded float-point numbers
> > of real spatial extent of the whole raster table coverage would do the trick,
> > and without touching headers of individual rasters in rows.
> We could do that and thus behave like the regular_blocking constraint
> which does no actual constraining.  Though I'd rather just store the
> "true" data extent as a geometry instead of having to compute it from
> numbers.


> All this can be done for 2.1.  I don't believe this can be done for
> 2.0 as it would be introducing 3 new constraint management functions
> and modifications to AddRasterConstraints() and
> DropRasterConstraints().

Maybe there could be a couple new functions instead of modifications
of the two existing ones. But I still don't understand how it worked
before the regression was introduced. How did the original extent ever
get into raster_columns ? Didn't raster2pgsql take care of that ?


More information about the postgis-devel mailing list