Re: Release plan

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>, <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Release plan
Date: 2003-05-01 15:11:44
Message-ID: 03AF4E498C591348A42FC93DEA9661B83AF06A@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas(dot)Pflug(at)web(dot)de]
> Sent: 01 May 2003 15:52
> To: Dave Page; pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: Release plan
>
>
> Dave Page wrote:
>
> >Do you want to take the responsibility of getting the dump slightly
> >wrong and someone finding they've lost their data or it's been
> >corrupted? I certainly don't. If however, we can build in
> pg_dump, or
> >provide a front end to it and display suitable messages whenever we
> >find a version mismatch, then I would be a lot more happy to include
> >such functionality.
> >
> >
> I don't have problems taking the responsibility. If I'm being
> paid to do
> so...

:-) Same here, but I'm not...

> If the "backup wizard" isn't smart enough to cope with potential user
> handling problems it's obviously not worth being integrated into
> pgadmin3 :-)

It's not so much the users as us. It's easy to get the SQL regeneration
slightly wrong, or export data in a slightly incompatible format. Why
recreate all those problems already solved by the pg_dump maintainers?
Perhaps we can get the guts of pg_dump compiled into a library though
and use that tried and test code with our own GUI?

Regards, Dave.

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2003-05-01 15:14:30 Re: Release plan
Previous Message Josh Berkus 2003-05-01 15:06:13 Re: Release plan