Restore error -- database escape problem?

[pfaffman (Jay Pfaffman)]

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.

[2016-09-01 21:58:56] Current version: 20160727233044
[2016-09-01 21:58:56] Restored version: 20160727233044

. . .

[2016-09-01 21:59:05] ERROR: unrecognized configuration parameter “row_security”
[2016-09-01 21:59:05] ERROR: current transaction is aborted, commands ignored until end of transaction block

. . .
A bunch of these:

[2016-09-01 21:59:09] invalid command \N

and stuff like this:

[2016-09-01 21:59:09] ERROR: syntax error at or near “2”
[2016-09-01 21:59:09] LINE 1: 2 ‘discuss’:2 ‘jewelri’:1 Jewelry Discussion en

[2016-09-01 21:59:10] ERROR: syntax error at or near “your”
[2016-09-01 21:59:10] LINE 1: your content is not getting advertised via unwanted electron…

It looks like somehow the database is configured such that stuff isn’t getting escaped properly?

[codinghorror (Jeff Atwood)]

Any ideas here @tgxworld?

[sam (Sam Saffron)]

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

[pfaffman (Jay Pfaffman)]

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

[codinghorror (Jeff Atwood)]

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

[pfaffman (Jay Pfaffman)]

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.

[Falco]

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