Hi, thanks for trying. Yes the backup included the invalid data, but we've just found the problem.
The 'special' characters in the data are handled just fine, but not if they are present in the column names. So does pgAdmin handle both data differently or is it Postgres? I thought if the db is encoded UTF8 the this wouldn't be a problem. best Nanina Am 08. Januar 2019 um 18:16 schrieb Dave Page <dp...@pgadmin.org>: On Tue, Jan 8, 2019 at 8:55 PM Nanina Tron <nanina.t...@icloud.com> wrote: Hi, yes thank you I will scan the table so at least I will see the 'bad' characters. We will see how many there are. Sorry, i forgot to append the data. Thanks. Did that include the "bad" data? I can load it just fine into a SQL_ASCII database (which I'd expect, as there's no encoding checks), or a UTF-8 database, and I can successfully export the table in both cases. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
