Upgrade from Prisma Postgres EA to GA - pg_dump Connection Error
Hi, I'm trying to upgrade from Prisma Postgres Early Access (EA) to General Availability (GA).
According to the documentation, I need to create a backup of my existing database using pg_dump. However, when running the following command:
futbolovo % PGSSLMODE=disable \
pg_dump \
-h 127.0.0.1 \
-p 5432 \
-Fc \
-v \
-d postgres \
-f ./mydatabase.bak \
&& echo "-complete-"
I get the following errors:
==============================
hostname: 127.0.0.1
port: 5432
username: <anything>
password: <none>
==============================
⏩ Establishing a new connection...
✅ Connection established
💥 TCP socket error: Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {
errno: -54,
code: 'ECONNRESET',
syscall: 'read'
}
✖️ Connection closed { code: 1005, reason: '' }
pg_dump: error: connection to server at "127.0.0.1", port 5432 failed: received invalid response to GSSAPI negotiation: R10 Replies
You selected the carefully hand-crafted route. A dev artisan will respond soon. Meanwhile, the
#ask-ai channel awaits if you're curious!Hey @mycak
Is this happening for project named "futbolovo"?
yes
and here gh repo => https://github.com/mycak/futbolovo
GitHub
GitHub - mycak/futbolovo: Interactive football map
Interactive football map. Contribute to mycak/futbolovo development by creating an account on GitHub.
@mycak Can you confirm the version of pg_dump you are using? Is it v16? You can check the version by running command
pg_dump --version
Also, you are running this command exactly like this right?
I am asking because we are able to reproduce the error you faced if we remove PGSSLMODE=disable line from the commandversion 14.15, yes that one commad:
PGSSLMODE=disable \
pg_dump \
-h 127.0.0.1 \
-p 5432 \
-Fc \
-v \
-d postgres \
-f ./mydatabase.bak \
&& echo "-complete-"
Can you please install v16 and try?
If you are on mac then you can install it with these commands
You may need to unlink postgres@14, which you can do by running
brew unlink postgresql@14
Because EA database is using postgres 16, the version mismatch could be causing this issue
with 16.x it works thanks!
I am glad to hear that!
Please let me know in case you run into any other issues.