diff options
| author | Robert Haas <rhaas@postgresql.org> | 2017-08-04 19:33:01 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2017-08-04 19:33:01 -0400 |
| commit | ff98a5e1e49de061600feb6b4de5ce0a22d386af (patch) | |
| tree | 9ceffad35527c7b3be5479dfcd2efec769f0e472 /src/tutorial/advanced.source | |
| parent | 03378c4da598840b0520a53580dd7713c95f21c8 (diff) | |
| download | postgresql-ff98a5e1e49de061600feb6b4de5ce0a22d386af.tar.gz postgresql-ff98a5e1e49de061600feb6b4de5ce0a22d386af.zip | |
hash: Immediately after a bucket split, try to clean the old bucket.
If it works, then we won't be storing two copies of all the tuples
that were just moved. If not, VACUUM will still take care of it
eventually. Per a report from AP and analysis from Amit Kapila, it
seems that a bulk load can cause splits fast enough that VACUUM won't
deal with the problem in time to prevent bloat.
Amit Kapila; I rewrote the comment.
Discussion: http://postgr.es/m/20170704105728.mwb72jebfmok2nm2@zip.com.au
Diffstat (limited to 'src/tutorial/advanced.source')
0 files changed, 0 insertions, 0 deletions