Re: Server/Data Migration Advice

From: Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>
To: PostgreSQL <pgsql-general(at)postgresql(dot)org>
Subject: Re: Server/Data Migration Advice
Date: 2011-12-15 14:55:46
Message-ID: CAAQLLO7ERTH4rWeDiRNS8fLh6p85uK8DDug9x3YCkVp_ssbFuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 15, 2011 at 9:37 AM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mike Christensen 2011-12-15 15:08:13 Re: Correct syntax to create partial index on a boolean column
Previous Message Adrian Klaver 2011-12-15 14:44:53 Re: question about \encoding option of psql