Hi,
How can I upgrade to latest postgresql version 9.2 from my current version
7.4.3? How complicated this will be as the db contains large amount of data? I
have installed the latest version 9.2 in new server and while restoring the
dump from old version, data in some of the large tables are
On 5/9/2013 2:02 AM, Arun P.L wrote:
pg_restore: [archiver (db)] Error from TOC entry1550 TABLE DATA
*table_name*;
pg_restore: [archiver (db)] COPY failed for table *table**_name*:
ERROR: invalid byte sequence for encoding UTF8: 0xa0
What else can I do for this issue, or in general how can
2013/5/9 Arun P.L aru...@hotmail.com:
Hi,
How can I upgrade to latest postgresql version 9.2 from my current version
7.4.3? How complicated this will be as the db contains large amount of data?
I have installed the latest version 9.2 in new server and while restoring
the dump from old
Since there was some issue with hotmail I couldn't reply earlier.
Encoding in version 7.4 was SQL_ASCII. What's the best way to deal with this?
I hope changing the encoding to UTF-8 while taking dump will work.
Surely I will have an eye on release notes in order to deal with the
typecasting
On 5/9/2013 9:12 PM, Arun P.L wrote:
Since there was some issue with hotmail I couldn't reply earlier.
Encoding in version 7.4 was SQL_ASCII. What's the best way to deal
with this?
I hope changing the encoding to UTF-8 while taking dump will work.
SQL_ASCII means that postgres has no
Hi,
And the way to deal with this? Any ideas on that? Whether changing encoding to
utf-8 in dump work?
Regards~
Arun
Arun P.L aru...@hotmail.com writes:
And the way to deal with this? Any ideas on that?
If you were happy with SQL_ASCII encoding before, keep using it.
Other encoding choices are basically constraints to ensure your
data is valid according to that encoding --- if you don't feel
like trying to
On Thu, May 9, 2013 at 9:41 PM, Arun P.L aru...@hotmail.com wrote:
Hi,
And the way to deal with this? Any ideas on that? Whether changing
encoding to utf-8 in dump work?
Yes, run initdb -E SQL_ASCII
This will create your database cluster with no encoding restrictions.
Whether this is a