a dump can be
implemented as a flag to pg_dump or even better as a default behavior.
Thank you,
Sergei Agalakov
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
It can be done of course, but as you can see in my examples the
statements in pg_dump generated scripts are grouped together by the objects.
It is easier to analyze the differences when all these differences for
an object are clustered together, and aren't dispersed in the diff file.
It also wil
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.
A
ifferences between them?
Sergei
> On Apr 17, 2016, at 12:41 PM, Sergei Agalakov
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
y has
done something manually - good for you, you are lucky guy then.
I did.
Sergei
On Sun, 17 Apr 2016 14:10:50 -0600
Sergei Agalakov wrote:
> 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 inste
imilar functionality?
:-)
Sergei
On 04/17/2016 01:10 PM, Sergei Agalakov wrote:
> 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 SQLWorkbe
Thank you, I know this place.
I just wanted to check that my request will have the peoples support.
So far it doesn't. It looks like that or people never need to compare
two PG databases to find the differences in the schemas or security,
or happy to use the third party tools to do it, and don't
