Re: Unable to dump database using pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: adear(at)usnx(dot)net
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org
Subject: Re: Unable to dump database using pg_dump
Date: 2008-06-11 22:34:09
Message-ID: 15010.1213223649@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adam Dear <adear(at)usnx(dot)net> writes:
> I'm not seeing the madisoncounty user in there.

Odder and odder. It might be worth trying "vacuum freeze pg_shadow".

> Also, I tried starting
> the db using /etc/init.d/postgres start, and it fails.

Fails how? In particular, what shows up in the postmaster log?

> Is that the
> proper way to get the service going, or should I be doing something else?

The usual way to manually start/stop daemons on Linux is

sudo /sbin/service postgresql start
sudo /sbin/service postgresql stop

(omitting sudo if you're already root). I'm not sure offhand if there's
any real difference between that and just calling the init.d script
directly, but I believe that's how you're Supposed To Do It.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Lambert 2008-06-11 22:39:13 Re: Determining offsets to jump to grab a group of records
Previous Message David Wilson 2008-06-11 22:29:18 Re: Determining offsets to jump to grab a group of records