Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 0E8C92E005F for ; Fri, 23 May 2008 16:24:03 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 77357-02 for ; Fri, 23 May 2008 16:23:54 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by developer.postgresql.org (Postfix) with ESMTP id C3B8E2E004A for ; Fri, 23 May 2008 16:23:56 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id n4so777353wag.5 for ; Fri, 23 May 2008 12:23:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=D1qlo/IPvJ+vRalQfHq2TjFdMA8MW/rBjb7ktoI6xNg=; b=kxv5AUyGTSLmK7Csk10n/mh3DLbsQkYRTigHQf7iGzrIdTKxlgsdKUcGw2VDzbs4KLmk9krY7jru54Us+wmYoUS/UzJYfljPAtQBd4aMMpqEyEss1WsFEuwTe7QJPA1j2winmQRxJsZwCuUxb5L2xto8wRS8hOh1x6b1eyvLyh0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hzgjAVPYgBcJZMYR/VscOpolgShPRdxRfyPhoUo2x9SkSsvrmxAxN+CwgbBDEaocNzJi5NkIDyKona2t80RdkXARkeyLZsVMs3pOD4eS8g/LyQfMdSS5d/5tAYW1klbWM1hYlFM+El3CddIpVDlciP9whSbsUEWyoowtybaUWHI= Received: by 10.114.113.1 with SMTP id l1mr2174988wac.226.1211570634890; Fri, 23 May 2008 12:23:54 -0700 (PDT) Received: by 10.114.130.17 with HTTP; Fri, 23 May 2008 12:23:54 -0700 (PDT) Message-ID: Date: Fri, 23 May 2008 13:23:54 -0600 From: "Scott Marlowe" To: "Carol Walter" Subject: Re: Continuing issues... Can't vacuum! Cc: "Jeff Frost" , pgsql-admin@postgresql.org In-Reply-To: <8F6322F3-A686-4535-B30A-0925DC803B5C@indiana.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5897F703-1525-477B-8749-80A0A4E0A656@indiana.edu> <483706BA.1080403@frostconsultingllc.com> <8F6322F3-A686-4535-B30A-0925DC803B5C@indiana.edu> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/208 X-Sequence-Number: 29292 On Fri, May 23, 2008 at 1:08 PM, Carol Walter 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?