Tim Gustafson wrote:
> Is there any way to change the character set of a database and its tables?
>
> I did a pg_dumpall to upgrade from Postgres 8.4 to Postgres 9.2, and
> all the tables came back as UTF-8, and now Bacula is complaining that
> it wants SQL_ASCII encoding for everything. I don'
Tim Gustafson writes:
> I'm curious why a pg_dumpall from 8.4 followed by a restore in 9.2
> caused the character sets to change at all. Was there some change in
> the default character sets between 8.4 and 9.2?
I was wondering that too. You did use pg_dumpall, and not individual
pg_dumps per d
On Tue, Feb 12, 2013 at 6:02 PM, Tim Gustafson wrote:
>> What you're looking for is to change the encoding, right, and not the locale?
>
> Correct.
>
>> You can't change the encoding of a database, but you can use a
>> different one when you create it - this can be specified in the CREATE
>> DATAB
> What you're looking for is to change the encoding, right, and not the locale?
Correct.
> You can't change the encoding of a database, but you can use a
> different one when you create it - this can be specified in the CREATE
> DATABASE statement.
That's what I wound up doing.
> You can also a
On Tue, Feb 12, 2013 at 5:34 PM, Tim Gustafson wrote:
> Is there any way to change the character set of a database and its tables?
>
> I did a pg_dumpall to upgrade from Postgres 8.4 to Postgres 9.2, and
> all the tables came back as UTF-8, and now Bacula is complaining that
> it wants SQL_ASCII e
Is there any way to change the character set of a database and its tables?
I did a pg_dumpall to upgrade from Postgres 8.4 to Postgres 9.2, and
all the tables came back as UTF-8, and now Bacula is complaining that
it wants SQL_ASCII encoding for everything. I don't see a flag on
pg_dumpall or pg_
