We've done a bit more digging on this issue and I think I know what's happening now.
The frequent NOTICE messages in the server log are related to a PostgreSQL function call from a PHP script in one of our web applications. The function issues ST_IsValid against a column in a table that has many invalid geometries. The function uses dblink to access the table because it resides in a different PostgreSQL database than the one in which the function resides. If I run the SQL from the function directly in the database in which the table lives, no NOTICE is sent to the server log. If I execute the function in the database (in which the function lives), I get the NOTICE messages in the server log. So I think this is a dblink issue, and PostGIS was a red herring. Shira On Wed, Jan 22, 2014 at 9:02 AM, Shira Bezalel <[email protected]> wrote: > Okay, show log_min_messages returns 'warning'. > > Shira > > > On Wed, Jan 22, 2014 at 7:29 AM, Sandro Santilli <[email protected]> wrote: > >> On Wed, Jan 22, 2014 at 07:18:03AM -0800, Shira Bezalel wrote: >> > Hi Sandro, >> > >> > show client_min_messages returns 'notice', but that parameter shouldn't >> > affect what is written to the log, correct? >> >> You're right, check >> >> show log_min_messages; >> >> As Paul said, PostGIS uses PostgreSQL facilities, not its own... >> >> --strk; >> _______________________________________________ >> postgis-users mailing list >> [email protected] >> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users >> > > > > -- > Shira Bezalel > Systems & Database Manager > San Francisco Estuary Institute > www.sfei.org > Ph: 510-746-7304 > > > -- Shira Bezalel Systems & Database Manager San Francisco Estuary Institute www.sfei.org Ph: 510-746-7304
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
