Thanks for all the suggestions. COPY may work for my purposes. The
SSH tunnel option for using pg_dump is very interesting.
Thanks!
Scott
On Jul 26, 2010, at 9:18 AM, David Fetter wrote:
> On Mon, Jul 26, 2010 at 08:58:59AM -0700, Scott Frankel wrote:
>>
>> Hi all,
>>
>> Is it possible to perform an SQL Dump without using pg_dump?
>
> No, but there may be more options for using pg_dump than you have
> looked at. One example would be to use pg_dump on one with an SSH
> tunnel to the other one's local PostgreSQL port (5432 by default, but
> check which yours is). For example:
>
> ssh -fNR 5432:localhost:5555 postgres@your.host.dom
>
> would let you connect to localhost:5555 with pg_dump and any other
> PostgreSQL tools.
>
> Cheers,
> David.
>> I have a special case situation wherein my application has access to
>> a remotely-hosted PG (8.3) database, but does not have access to its
>> admin tools. (There's a longer backstory here that I'm happy to
>> explain if necessary.) I'm looking for an efficient way to dump all
>> the data in the DB without having to SELECT * on each table.
>>
>> Thanks in advance!
>> Scott
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>
> --
> David Fetter <david@fetter.org> http://fetter.org/
> Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> Skype: davidfetter XMPP: david.fetter@gmail.com
> iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate
>