Restore error -- database escape problem?

(Jay Pfaffman) #1

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?

Upgrade failed due to unclean database shutdown
(Jeff Atwood) #2

Any ideas here @tgxworld?

(Sam Saffron) #3

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

(Jay Pfaffman) #4

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

(Jeff Atwood) #5

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

(Jay Pfaffman) #6

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.

(Rafael dos Santos Silva) #7

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