The issue requires to be investigated further, for now please find the following documentation to follow:
- Postgres best practices [1] - Creating instances [2] - Release notes [3] - Connecting to Cloud SQL - connection with Unix sockets [4] [1] https://cloud.google.com/sql/docs/postgres/best-practices [2] https://cloud.google.com/sql/docs/postgres/create-instance [3] https://cloud.google.com/sql/docs/postgres/release-notes [4] https://cloud.google.com/sql/docs/postgres/connect-app-engine-standard#connecting_to On Saturday, December 25, 2021 at 10:10:31 AM UTC-5 Dave Stone wrote: > Hi all; I've racked my brains & read much docs but still nada.. so hoping > for any pointers. > > Want another DB in parallel to upgrade things (PG 12, to 14). PG12 works > fine, App Engine (flex, Node 16), Cloud Functions (Node 16; Python 3) and > local proxy all zero issues. > > Update deploy script to new PG version, and run. Lovely new DB. Local > proxy connects, grand. Redeploy Cloud Functions to pickup env vars, > connects, grand (both Node & Python connect & run). Redeploy App Engine > with new beta_settings name & env vars... and nope. > > ``` > connect ENOTDIR /cloudsql/foobar:us-central1:foobar/.s.PGSQL.5432" > ``` > > As-if the unix socket isn't there? Everything seems to look similar, > instance, IAM, etc. Rename env vars & beta_settings back to old, works > fine. Rename back to new, nope.. > > What am I missing? Thanks in advance for ANY ideas, as I'm out :S > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2367f340-4a89-42d1-b0b7-a43fd6b201ean%40googlegroups.com.
