diff options
author | Yedidyah Bar David <didi@redhat.com> | 2018-12-04 13:10:32 +0200 |
---|---|---|
committer | Bryn M. Reeves <bmr@redhat.com> | 2018-12-12 10:02:36 +0000 |
commit | 254d93499d64acaff5103e15c25649d418004737 (patch) | |
tree | e5fb5bb3b8dcd06284cafafaa0129457e7e0ccf7 /requirements.txt | |
parent | 47e6b3d92c8a13560b248e6f0e2ffb334b547d07 (diff) | |
download | sos-254d93499d64acaff5103e15c25649d418004737.tar.gz |
[postgresql] Do not limit dump size
In principle, this might be risky - if a database is huge, we might not
want to collect all of it. But there is no sense in collecting only its
tail. If this turns out problematic, a future patch might check db size
and do not collect it at all if it's too large.
Bug-Url: https://bugzilla.redhat.com/1654068
Resolves: #1497
Signed-off-by: Yedidyah Bar David <didi@redhat.com>
Signed-off-by: Bryn M. Reeves <bmr@redhat.com>
Diffstat (limited to 'requirements.txt')
0 files changed, 0 insertions, 0 deletions