From: Scott Marlowe <scott.marlowe@gmail.com>
To: Carol Walter <walterc@indiana.edu>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Continuing issues... Can't vacuum!
Date: Fri, 23 May 2008 13:23:54 -0600
Message-ID: <dcc563d10805231223n64368b1bh1e5de39a1850cd4c@mail.gmail.com> (raw)
In-Reply-To: <8F6322F3-A686-4535-B30A-0925DC803B5C@indiana.edu>
References: <5897F703-1525-477B-8749-80A0A4E0A656@indiana.edu>
<483706BA.1080403@frostconsultingllc.com>
<8F6322F3-A686-4535-B30A-0925DC803B5C@indiana.edu>
On Fri, May 23, 2008 at 1:08 PM, Carol Walter <walterc@indiana.edu> wrote:
> Jeff,
>
> Thank you very much. I didn't know about this command. There are lots of
> times this would have saved me looking it up in my documentation. I've got
> a couple of different instances of postgres running and I always have to
> check the docs to find out where my config file is.
>
> Well, the table I told everyone about yesterday won't let me run pg_dump
> against it. My hesitancy comes from not knowing what the result will be of
> dumping the other databases. I've had the experience of dumping my "can of
> worms" out and not getting them back in the same "can" when I was done with
> them. =)
What error are you getting when you try to dump that table?
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: scott.marlowe@gmail.com, walterc@indiana.edu, jeff@frostconsultingllc.com
Subject: Re: Continuing issues... Can't vacuum!
In-Reply-To: <dcc563d10805231223n64368b1bh1e5de39a1850cd4c@mail.gmail.com>
* 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