I’m having trouble restoring to a hosted site. It restored fine on my Droplet, but not at the place that’s hosting Discourse for a client. I suppose it’s their problem to figure out, but I’m curious about what it could be. . . . . . . A bunch of these: and stuff like this: It looks like somehow the database is configured such that stuff isn’t getting escaped properly?

Oh. Golly. That sounds painful to resolve. But that sounds like a likely explanation. Thanks.

So check Postgres versions on both sides and make sure they match.

The hosting company switched to the same Postgres I had used. It’s troublesome that PG is so finicky about restoring across versions. I guess it happens rarely enough that it’s not worth trying to catch it.

I think it’s the row security from last version that made the dumps not compatible.

Restore error -- database escape problem?

Product Support

sam (Sam Saffron) September 2, 2016, 12:27am 3

I have seen this before … I think its related to trying to restore incompatible versions of pg.

Topic		Replies	Views
Restoring backup fails due to Postgres version mismatch Self-hosting	5	3430	February 14, 2019
Can't restore saved backup Self-hosting	3	1385	March 7, 2017
Error when restore DB backup Self-hosting	25	2269	August 23, 2018
Restoring backup from 2.0.0.beta5 disables Discourse Bug	7	1262	April 12, 2018
Database issues migrating form old version 20150822141540 Self-hosting	13	1312	September 22, 2022

Restore error -- database escape problem?

Related topics