Connecting through psql not accepting unix socket

[rikusen0335]

Question

Connecting through psql not accepting unix socket, but tcp accepts.
Did I miss something?

Additional Context

This is similar issue but I'm really sure I am not using wrong connection name.

I was also reading about this and this

Reproducing

1. sudo mkdir /cloudsql; sudo chmod 777 /cloudsql
2. ./cloud_sql_proxy -dir=/cloudsql shows:

2022/01/12 02:57:02 current FDs rlimit set to 524288, wanted limit is 8500. Nothing to do here.
2022/01/12 02:57:04 Using gcloud's active project: [PROJECT_ID]
2022/01/12 02:57:09 Listening on /cloudsql/PROJECT_ID:REGION:INSTANCE_NAME for PROJECT_ID:REGION:INSTANCE_NAME
2022/01/12 02:57:09 Ready for new connections
2022/01/12 02:57:10 Generated RSA key in 502.627252ms

3. Copy and paste PROJECT_ID:REGION:INSTANCE_NAME to use psql "sslmode=disable host=/cloudsql/PROJECT_ID:REGION:INSTANCE_NAME user=DB_USER"
4. Then got:

psql: error: could not connect to server: Not a directory
        Is the server running locally and accepting
        connections on Unix domain socket "/cloudsql/PROJECT_ID:REGION:INSTANCE_NAME/.s.PGSQL.5432"?

[rikusen0335]

I am not sure if this is a bug, so I opened this as a question. I just make it sure.

[enocom]

This is a bug which seems to have been introduced in v1.26.0. I'll work on a fix. Thanks for the report.

[enocom]

The change in 480992a introduced this bug inadvertently.

[enocom]

Upon further research, I've found this is a bug in the Connect API. I've filed an internal bug to get this fixed quickly.

[enocom]

In short, the Connect API is not returning DatabaseVersion for Postgres 14 instances and so the proxy does not know to use the correct file path for the Unix socket.

EDIT: This affects Postgres 14 instances only.

[enocom]

@rikusen0335 What version of Postgres are you using?

[rikusen0335]

@enocom
Sorry for late, I am using Postgres 14 on Cloud SQL.

[enocom]

Until this is fixed I recommend using a TCP socket to connect like this:

cloud_sql_proxy -instances=<INSTANCE_CONNECTION_NAME>=tcp:5432

[enocom]

This is fixed now and all regions are reporting a database version for pg14.