From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Eric Svenson <esvenson74(at)googlemail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Fwd: Fwd: Problem with pg_dump and decimal mark |
Date: | 2014-12-10 14:27:51 |
Message-ID: | 54885867.1020605@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/10/2014 01:32 AM, Eric Svenson wrote:
> So, one more success...
>
> I have taken a part of the backup SQL file which fills the table
>
> COPY dev_my_settings (.....) from stdin;
> 12345 text text 0 123.345345
>
> This file ALONE works! (without changing ANYTHING!)
Hmm, almost like the encoding/locale is changing in the complete file.
>
> So if I run the first (huge) SQL file and then the second, which fills
> the dev_my_settings table, everything is ok.
FYI if you do a pg_dump using the custom format(-Fc) you have more
control over the restore. You can run pg_restore -l against the dump
file to get a Table of Contents(TOC), which you can edit by commenting
out items you do not want to restore and then feed back to pg_restore
via -L. You also have the option to 'restore' all or part of the custom
file to a text file using the -f option. The details can be found here:
http://www.postgresql.org/docs/9.3/interactive/app-pgrestore.html
>
> 2014-12-10 10:23 GMT+01:00 Eric Svenson <esvenson74(at)googlemail(dot)com
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2014-12-10 14:49:12 | Re: Idle Sessions inTransaction with RELEASE_EXEC_SVP queries and locks |
Previous Message | Adrian Klaver | 2014-12-10 13:56:26 | Re: Error : Ensure this value has at most 30 characters (it has 31) django |