pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tim Perdue <perdue@raccoon.com>
To: Bruce Momjian <maillist@candle.pha.pa.us>
To: pgsql-sql@hub.org
Subject: Re: [SQL] Re: [HACKERS] URGENT -
Date: Mon, 15 Mar 1999 18:39:52 -0600
Message-ID: <001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net> (raw)

I still cannot get pg_dump to work since I fixed the system yesterday. This
is a real mess and I need to make sure I have a current backup.

-I upgraded from 6.4 -> 6.4.2 and applied the 2GB patch
-I did "initdb" from the postgres user account
-I cannot get pg_dump to work:


-------
[tim@db /]$ pg_dump db_domain > /fireball/pg_dumps/db_domain.dump
pg_dump error in finding the template1 database
-------


At this point, the postmaster dies and restarts.

I think I'm getting to where I need some real help getting this thing to
dump again.

The database is up and running just fine - I just cannot dump.

Any tips or advice is GREATLY needed and appreciated at this point. All I
need is it to take a dump ;-)

Tim

tim@perdue.net





-----Original Message-----
From: Bruce Momjian <maillist@candle.pha.pa.us>
To: tim@perdue.net <tim@perdue.net>
Date: Monday, March 15, 1999 11:57 AM
Subject: Re: [SQL] Re: [HACKERS] URGENT -


>>
>>
>> >From 6.4 -> 6.4.2
>>
>> The production database is working well, but pg_dump doesn't work. Now
>> I'm worried that my database will corrupt again and I won't have it
>> backed up.
>
>6.4 to 6.4.2 should work just fine, and the patch should not change
>that.  Are you saying the application of the patch caused the system to
>be un-dumpable?  Or perhaps was it the stopping of the postmaster.  I
>can work with you to get it dump-able if needed?
>
>--
>  Bruce Momjian                        |  http://www.op.net/~candle
>  maillist@candle.pha.pa.us            |  (610) 853-3000
>  +  If your life is a hard drive,     |  830 Blythe Avenue
>  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>




view thread (2+ messages)  latest in thread

Message-ID: <001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net>
Permalink:  ../001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net/
Also on:    postgresql.org/message-id/001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: perdue@raccoon.com, maillist@candle.pha.pa.us, pgsql-sql@hub.org
  Subject: Re: [SQL] Re: [HACKERS] URGENT -
  In-Reply-To: <001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net>
  References: <001701be6f45$81d4dc30$0b8c5aa5@timnt.weather.net>

* 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