I performed a binary search and found out, that 12.12 stil works but 14.5 already doesn't work. Waiting for your suggestions, I'd prefer to keep jdbc 0.7.12

I use postgres:15.0-alpine3.16 and it works for me

I use jdbc next

with HikariDataSource as pool

com.github.seancorfield/next.jdbc {:mvn/version "1.3.834"}

com.zaxxer/HikariCP {:mvn/version "5.0.1"}

org.postgresql/postgresql {:mvn/version "42.5.0"}

Oh, thanks. Maybe I also can rewrite all the project to jdbc next, but unfortunatelly it uses different incompatible api and will not work as direct dependency substitute 😕

I think next jdbc is really good choice

But refactoring is a job to do. Worth or not worth it,

Maybe, but I entered realy legacy project with Postgres 9.6 and previous jdbc/honeysql community (not Sean Cornfield) versions with different apis....

yeah it is live 🙂

(let [db "jdbc:"
      ds (jdbc/get-datasource db)
      _ (prn :ds ds)]
  (jdbc/get-connection ds))

:ds #object[next.jdbc.connection$url_PLUS_etc$reify__21688 0x73f9c24 "jdbc:"]
Syntax error (PSQLException) compiling at (.repl-input:1:1).
The authentication type 10 is not supported. Check that you have configured the pg_hba.conf file to include the client's IP address or subnet, and that it is using an authentication scheme supported by the driver.

What I do wrong?

https://stackoverflow.com/questions/64210167/unable-to-connect-to-postgres-db-due-to-the-authentication-type-10-is-not-suppor

Do you keep you old DB config after upgrade postgresql?

What is db config? )

Does it work for you if you will run fresh new postgresql?

without any volume in docker etc.

I just installed different docker pg images

It works if I start docker container with 9.6, up to 12.12

My guess is in the new version they turned off by default some legacy way of auth

and what you need to to do is what stackoverlow saying

or upgrade clojure deps

to for example jdbc next 🙂

I use jdbc next - it shows above

:ds #object[next.jdbc.connection$url_PLUS_etc$reify__21688 0x73f9c24 "jdbc:"]

next.jdbc.connection

Can you cat docker-compose.yaml ?

I do not use compose, I use hub images

docker run --name heron-pg-15.0 -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=password -e POSTGRES_DB=heron -d postgres:15.0

(jdbc-connection/->pool HikariDataSource {:jdbcUrl uri
                                                                                     :maximumPoolSize 2
                                                                                     :poolName "historical data"})

(:import (com.zaxxer.hikari HikariDataSource))

and later you can use what this fn return as a “connectable”

as a first parameter in jdbc

I tried without hikari pools, just create connection object for beginning

and I use postgres:15.0-alpine3.16 you can try this one

Give me 5 mins I'l try your version

\q

soory, wrong keyboard )))

The same error

Going to dig into your SO link

that is very strange, it has to be something what you miss

this image works with next jdbc

at least on my computer 😉

Did you also upgrades other dependencies? https://clojurians.slack.com/archives/C1Q164V29/p1667393059639219?thread_ts=1667390245.142989&cid=C1Q164V29

Yep, 42/5/0

try new app maybe? Maybe some of you dependency blow up it. Like legacy jdbc dependency or something

I think creating new empty project will answer that

Just tested that regular (not next) jdbc and pg 42.5.0 works fine together on 9.6

Andrey Ivanov, [02.11.2022 20:36]
(let [uri "jdbc:"
        conn (jdbc/add-connection uri (jdbc/get-connection uri))]
    (jdbc/query conn ["select version()"]))

Andrey Ivanov, [02.11.2022 20:36]
({:version "PostgreSQL 9.6.24 on x86_64-pc-linux-gnu (Debian 9.6.24-1.pgdg90+1), compiled by gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516, 64-bit"})

Maybe will try new project after trying SO soggestions with configs magic...

Oh my, created new empty project and looks like both jdbc libs works with postgres 15... At least connection creates and query version works. Thanks for the idea, will look what may break it in working project...

Just catching up on this: use of c.j.j vs next.jdbc is irrelevant for this issue -- they're both thin wrappers around JDBC and what you are seeing is a JDBC level issue. Nothing to do with the Clojure libraries.

So you can stick with c.j.j for now.

Thanks! Yep, they both works on empty project without extra deps, but both fails if I added my working project deps to it 😁 But now I can use binary search and found the exact deps which are incompatible with it.

Without any context, what does that question even mean?

If COPY is a SQL statement, you don't need "support" in next.jdbc: it will run whatever SQL you give it.

https://www.postgresql.org/docs/current/sql-copy.html

yes, I can use it without jdbc, but I like to use jdbc 🙂

just brining a suggestion for a new feature

There is https://github.com/jgdavey/clj-pgcopy but I didn’t try

If that's a SQL command, you should be able to execute! it like any other SQL command.