Eric Lemoine <eric.lemoine@xxxxxxxxxxxx> writes: > The initial "select pc_typmod_pcid(1)" query completely screws the > connection. > "select pc_typmod_pcid(1)" is just an example of a simple query that > triggers the problem. There are many others. But it has to be a query > using the Pointcloud extension. My guess is that it's got nothing to do with the specific query, but that Pointcloud is installing some hook functions when it's loaded, and that one or another of those hooks is killing performance for subsequent queries, either by taking too long in itself or by defeating some important optimization. Hard to speculate further with just this much data. > I have no problem if I start with the main query (my "select points > from" query of interest). And running the "select pc_typmod_pcid(1)" > query in the middle does not cause any problem. It has to be run first > on the connection to do the harm. Have you experimented with other queries that don't involve PostGIS? I'm wondering if your hook-installation code fails to work properly unless PostGIS was loaded first. This would be easier to credit if there are hooks both extensions try to get into. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
