| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Carol Walter" <walterc(at)indiana(dot)edu> |
| Cc: | "Jeff Frost" <jeff(at)frostconsultingllc(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Continuing issues... Can't vacuum! |
| Date: | 2008-05-23 19:23:54 |
| Message-ID: | dcc563d10805231223n64368b1bh1e5de39a1850cd4c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, May 23, 2008 at 1:08 PM, Carol Walter <walterc(at)indiana(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Weber | 2008-05-23 19:35:38 | 1600 column limit per table |
| Previous Message | Carol Walter | 2008-05-23 19:08:39 | Re: Continuing issues... Can't vacuum! |