I don't see how these questions are related to the proposed pg_dump
improvement.
I suggest to improve pg_dump so it can be used instead of the third
party tools like DBSteward and SQLWorkbench/J etc.
to compare two different databases or existing dumps, and to identify
the differences. The use cases will be exactly
the same as for the third party tools. The positive difference will be
that pg_dump is a very reliable, always available and supports all the
latest PostgreSQL features.
Do you imply that there shouldn't be any reasons to compare different
databases to find the differences between them?
Sergei
> On Apr 17, 2016, at 12:41 PM, Sergei Agalakov <Sergei(dot)Agalakov(at)getmyle(dot)com> wrote:
>
> I know about DBSteward. I don't like to bring PHP infrastructure only to be able to compare two dumps,
> and to deal with potential bugs in the third party tools. The pg_dump in other hand is always here, and is always trusted.
> SQLWorkbench/J also can compare two schemas, and requires only Java. Again, I trust pg_dump more.
>http://www.sql-workbench.net/
>
> May be pg_dump was never INTENDED to generate the dump files with the determined order of the statements,
> but it CAN do it with the minor changes, and be more useful to administrators. Why rely on the third party tools
> for the tasks that can be done with the native, trusted tools?
>
> Sergei
Does it matter if they differ if you cannot recreate the correct one exactly from source-controllled DDL? Or know how they are supposed to differ if this is a migration point?
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
