[mapserver-users] problem with getcapabilities xml generation when layer is using data from postgresql inherited table

[Jeff McKenna]

I should also mention that for each of my PostgreSQL layers I always 
enable connection pooling for each LAYER:

   PROCESSING "CLOSE_CONNECTION=DEFER"

Although my notes don't answer your specific question, these are the 
steps that I always follow.

-jeff



-- 
Jeff McKenna
MapServer Consulting and Training Services
co-founder of FOSS4G
http://gatewaygeo.com/


On 2020-10-21 7:14 a.m., Zmitser Kozhukh wrote:
> Good time of the day, may be it is my misconception, but I used to think 
> that generation of GetCapabilities xml doesn’t require checking that the 
> data source of the layer is valid and it really has data etc. I was 
> thinking that this is just a matter of converting metadata from mapfile 
> to xml format by certain rules.
> But it appears, that it is different from what I have been thinking. I 
> am having a wms service that reads data from inherited postgresql table 
> (table inherits data from many thousands of childs table) and it takes 
> infinity to generate getcapabilities xml document:
> https://gis.lesprojekt.cz/cgi-bin/mapserv?map=/home/dima/maps/olu/european_openlandusemap.map&service=WMS&request=GetCapabilities
> With other wms services that use just ordinary tables as data source it 
> (this instance of mapserver) works just fine.
> So my questions is : is it possible to change the code of mapserver not 
> to check all child tables and instead just generate getcapabilities xml 
> from the metadata in mapfile?
> Or may be someone had this issue and found other solution?
> I think in older versions of mapserver (this concrete instance 
> is version 7.2.0 ) inherited tables didn’t cause any troubles.
> Sincerely, Dimitri
>