[postgis-tickets] [PostGIS] #2217: [raster] ST_AsBinary semantic discrepancy

[PostGIS]

#2217: [raster] ST_AsBinary semantic discrepancy
---------------------+------------------------------------------------------
 Reporter:  mloskot  |       Owner:  dustymugs
     Type:  defect   |      Status:  new      
 Priority:  medium   |   Milestone:           
Component:  raster   |     Version:  trunk    
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by mloskot):

 Replying to [comment:17 pracine]:
 > Replying to [comment:15 mloskot]:
 > > @pracine Database communication is based on client-server model. The
 fact that you can
 > > I'd also argue, that in distributed systems, in a cloud, returning
 local path is useless indeed. It is not responsibility of application to
 read the file registered in PostGIS database as out-db raster, but it is
 responsibility of PostGIS to serve that file. The application does not
 want to distinguish storage modes in the server.
 >
 > So even ST_BandPath() would be irrelevant in that case?

 IMO, yes.

 > So why storing raster outside the database then?

 For flexibility of storage, data organisation, performance tuning.
 PostgreSQL I/O to reach blobs of data is never as fast as direct
 filesystem I/O.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2217#comment:20>
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.