title: search_path doesn't work as expected with currentSchema in URL
body: <p>My SQL commands have issues finding objects from the <code>public</code> schema (which is in the default DB <code>search_path</code>) when specifying the <code>currentSchema</code> parameter in the DB connection URL. </p>
  
  <p>How could this be fixed? </p>
  
  <p>The long story:</p>
  
  <ol>
  <li>I have an application schema <code>app1</code>.</li>
  <li>The DB has the Postgis extension installed in the <code>public</code> schema (and we want to keep it there).</li>
  <li><p>The DB <code>search_path</code> is configured like this:</p>
  
  <pre><code>ALTER DATABASE tst SET search_path = "$user", public
  </code></pre></li>
  <li><p>When connecting to the DB without specifying current schema in URL, the default schema is public and so it finds all the geo functions and objects. But I have to specify the <code>app1</code> schema prefix when addressing objects from <code>app1</code>, e.g.:</p>
  
  <pre><code>select st_asgeojson(geometry,15,4) from app1.shapes limit 5
  </code></pre></li>
  <li><p>This is not convenient. So I added "app1" as a current schema parameter to the connection URL like this:</p>
  
  <pre><code>jdbc:postgresql://localhost:5432/tst?currentSchema=app1
  </code></pre></li>
  <li><p>Now, when I connect to the DB, I don't have to specify the app1 prefix when addressing objects from app1 schema. However, requests that involve Postgis objects don't work anymore and fail with:</p>
  
  <blockquote>
    <p>ERROR: function st_asgeojson(public.geometry, integer) does not exist</p>
  </blockquote></li>
  </ol>
  
  <p>My understanding is that it should search for the objects in the <code>search_path</code> and find them in the <code>public</code> schema but it doesn't happen for some reason. 
  I've tried specifying search path on a user level as well but it still didn't work.</p>