From: | johnf <jfabiani(at)yolo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: exporting postgre data |
Date: | 2008-01-25 16:51:47 |
Message-ID: | 200801250851.47644.jfabiani@yolo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday 25 January 2008 07:21:34 am Harald Armin Massa wrote:
> Bill,
>
> pgadmin3 provides the same: just dig down to the table, use the backup
> link and give the options. It also calls pg_dump just with the right
> parameters, you can copy that command for a .cmd for professional
> automatic backup.
>
> Best wishes,
>
> Harald
>
> > MSSQL has a fancy GUI "wizard".
> >
> > It basically does all the stuff pg_dump does, but just using a GUI
> > interface to manage all the options. I guess it has the addition
> > of managing the interaction between pg_dump on one server an pg_restore
> > on another as well.
> >
> > Doesn't really have any more features that I'm aware of, just has a
> > nice "one stop" interface.
> >
> > --
> > Bill Moran
> > http://www.potentialtech.com
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: explain analyze is your friend
The issue I have with pgAdmin3 and backing up a table is with the restore.
The associated sequences are not restored. Granted that might be a different
problem. But from a users perspective I see it as a major problem.
--
John Fabiani
From | Date | Subject | |
---|---|---|---|
Next Message | Luis Alberto Pérez Paz | 2008-01-25 16:57:18 | Re: Postgresql + digital signature |
Previous Message | Daniel Verite | 2008-01-25 16:50:41 | Re: best way to query |