Gone back to using 5433 and your java app can connect to that?
If that's the case, then maybe your java app had been changed to 5433 all along
and was a connection issue.
Search path is independent of port, but it can be set on a number of levels
1) at the session level
2) at the database,
Search path is set. Because it is set in the database it is independent of the
port, correct?
Because I need to move forward, I've gone back to using port 5433 and all is
working.
Thanks to all for taking the time to help.
Simon
39 Cliff View Drive
Allens Rivulet Tas 7150
(W) 0418 396
Yah that's one I forgot to mention.
Search paths can also be set by applications per session, so you might want
to make sure your java app is not doing that. I've been bitten by that with
some frameworks, where they have a search_path set which is different from
the one I set at the database or
What about search path for Postgres ? It could be different for each
client accessing Postgres.
Den 03-10-2022 kl. 20:27 skrev Regina Obe:
That is weird. I would have thought maybe a JDBC driver issue, but the error
suggests it was able to connect and just not able to access that function.
Sandro Santilli wrote (please quote with appropriate attribution):
> > This means that your current "default" PostGIS version is 2.4.9,
> > so "postgis_extensions_upgrade()" tries to upgrade to that version,
> > but it's actually a DOWNGRADE instead.
On Mon, Oct 03, 2022 at 11:05:53AM +0200,
