postgresql/src/bin
Tom Lane 40c333c39c Fix a performance problem in pg_dump's dump order selection logic.
findDependencyLoops() was not bright about cases where there are multiple
dependency paths between the same two dumpable objects.  In most scenarios
this did not hurt us too badly; but since the introduction of section
boundary pseudo-objects in commit a1ef01fe16,
it was possible for this code to take unreasonable amounts of time (tens
of seconds on a database with a couple thousand objects), as reported in
bug #11033 from Joe Van Dyk.  Joe's particular problem scenario involved
"pg_dump -a" mode with long chains of foreign key constraints, but I think
that similar problems could arise with other situations as long as there
were enough objects.  To fix, add a flag array that lets us notice when we
arrive at the same object again while searching from a given start object.
This simple change seems to be enough to eliminate the performance problem.

Back-patch to 9.1, like the patch that introduced section boundary objects.
2014-07-25 19:48:54 -04:00
..
initdb Translation updates 2014-07-21 00:58:58 -04:00
pg_basebackup Translation updates 2014-07-21 00:58:58 -04:00
pg_config Translation updates 2014-02-17 16:57:27 -05:00
pg_controldata Remove tabs after spaces in C comments 2014-05-06 11:26:26 -04:00
pg_ctl Translation updates 2014-07-21 00:58:58 -04:00
pg_dump Fix a performance problem in pg_dump's dump order selection logic. 2014-07-25 19:48:54 -04:00
pg_resetxlog Translation updates 2014-07-21 00:58:58 -04:00
pgevent Stamp copyrights for year 2011. 2011-01-01 13:18:15 -05:00
psql Translation updates 2014-07-21 00:58:58 -04:00
scripts Remove tabs after spaces in C comments 2014-05-06 11:26:26 -04:00
Makefile Make distprep and *clean build targets recurse into all subdirectories. 2011-07-03 13:55:27 -04:00