pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tena Sakai <tsakai@gallo.ucsf.edu>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: ian.lea@gmail.com <ian.lea@gmail.com>
Subject: Re: trouble restoring database
Date: Tue, 24 Aug 2010 21:25:38 -0700
Message-ID: <C899E952.C178%tsakai@gallo.ucsf.edu> (raw)
In-Reply-To: <AANLkTim0u4kHBUhFjQh28q3wccTUTRbppEzk27-WRC4m@mail.gmail.com>

Hi Scott,

Thank you for your quick tips.  I shall remember zcat (and
hopefully others).

Regards,

Tena Sakai



On 8/24/10 2:30 PM, "Scott Marlowe" <scott.marlowe@gmail.com> wrote:

> On Tue, Aug 24, 2010 at 3:22 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
>> Having said that, I think Ian is correct that I was missing -c flag in the
>> command below:
>>  gunzip ..../dumpall20100822.0.gz | /usr/local/pgsql/bin/psql -f - postgres
> 
> Quick tip, you can use zcat to get the output of a gzipped file like:
> 
> zcat ..../dumpall20100822.0.gz|psql
> 
> There's also zgrep, zless, zegrep, zxpdf, and zdiff.  All do what it
> looks like they do.
> 
> 
>> Since the file got uncompressed, I am now running the command:
>>  psql -f /home/tsakai/Notes/postgres/dumpall20100822.0
>> and I think it is working.  It is giving messsages:
>>  ERROR:  role "postgres" already exists
>>  STATEMENT:  CREATE ROLE postgres;
>>  ERROR:  database "testdb" already exists
>>  STATEMENT:  CREATE DATABASE testdb WITH TEMPLATE = template0 OWNER =
>> postgres ENCODING = 'UTF8';
>>  LOG:  checkpoints are occurring too frequently (5 seconds apart)
>>  HINT:  Consider increasing the configuration parameter
>> "checkpoint_segments".
>> 
>> 
>> The last 2 lines are repeated many, many times.  This is not terribly
>> Serious, is it?  (I will fix it via postgresql.conf file shortly.)
> 
> No.  It's just telling you that from a performance perspective things
> would be faster with more checkpoint segments.  Unless you spend a
> fair portion of your day restoring dbs, it's probably not big deal.
> If your machines only do a little writing at a time then you can
> probably leave it.  However, increasing checkpoint segments does help
> a lot if you do handle a fair bit of writes, and it's cheap and easy
> to do.




view thread (7+ messages)

Message-ID: <C899E952.C178%tsakai@gallo.ucsf.edu>
Permalink:  ../C899E952.C178%25tsakai@gallo.ucsf.edu/
Also on:    postgresql.org/message-id/C899E952.C178%tsakai@gallo.ucsf.edu

 · 

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: tsakai@gallo.ucsf.edu, scott.marlowe@gmail.com, Kevin.Grittner@wicourts.gov, ian.lea@gmail.com
  Subject: Re: trouble restoring database
  In-Reply-To: <C899E952.C178%tsakai@gallo.ucsf.edu>

* 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