pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mija Lee <mija@scharp.org>
To: pgsql-admin@postgresql.org
Subject: -d option in pg_dump
Date: Tue, 08 Jan 2008 12:32:23 -0800
Message-ID: <4783DDD7.2030900@scharp.org> (raw)

Hi -

In previous versions of postgres (8.1, 8.0), we had problems loading 
some data from dumps that were used the copy command rather than the 
insert command. If I remember correctly, these problems were caused by 
weird characters in some of the data values. As a result, we tend to use 
the -d option with pg_dump. At this point our databases are taking too 
long to reload using inserts. I did some testing and haven't run into 
the problems with the copy commands but don't want to find out that I 
was wrong when I'm trying to restore from a failure.

Were there changes made some time before 8.2.4 that made loading pg_dump 
with copy as safe as with insert commands? Have other people had 
problems restoring databases from pg_dump without the -d option?

Mija




view thread (2+ messages)  latest in thread

Message-ID: <4783DDD7.2030900@scharp.org>
Permalink:  ../4783DDD7.2030900@scharp.org/
Also on:    postgresql.org/message-id/4783DDD7.2030900@scharp.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: mija@scharp.org
  Subject: Re: -d option in pg_dump
  In-Reply-To: <4783DDD7.2030900@scharp.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox