Re: Server/Data Migration Advice - Mailing list pgsql-general

From Carlos Mennens
Subject Re: Server/Data Migration Advice
Date
Msg-id CAAQLLO7ERTH4rWeDiRNS8fLh6p85uK8DDug9x3YCkVp_ssbFuw@mail.gmail.com
Whole thread Raw
In response to Re: Server/Data Migration Advice  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: Server/Data Migration Advice
List pgsql-general
On Thu, Dec 15, 2011 at 9:37 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote:
> You know the fine manual covers this?:
> http://www.postgresql.org/docs/9.1/interactive/app-pgdump.html

I've honestly skimmed the manual and it's very easy to use and good
but it covers so many aspects and sometimes I need a specific answer
for my situation.

> In the case above you seemed to have used the plain text format, in the future
> should you use a non text format the restore process is here:
> http://www.postgresql.org/docs/9.1/interactive/app-pgrestore.html

Are you saying I dumped the database in a text formal or I'm restoring
the database infile in plain text? I'll read that 2nd URL link you
posted. What are the issues with using pg_dump to dump and then 'psql
some_db < pg_dump.sql'? I show the manual explains how to perform this
action and what the system is doing but doesn't explain why this is an
issue or why you recommended to use pg_restore instead?

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: question about \encoding option of psql
Next
From: Mike Christensen
Date:
Subject: Re: Correct syntax to create partial index on a boolean column