diff options
| author | Amit Kapila <akapila@postgresql.org> | 2020-12-04 13:54:50 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2020-12-04 13:54:50 +0530 |
| commit | 8ae4ef4fb0e0331f02c4615182600546c8e5c4d4 (patch) | |
| tree | 4de7d9c99d8fc7b72d5eec3cee914514c6bd04a2 /src/backend/access/gist/gist.c | |
| parent | bd94a9c04e04bb3b626e88981a50fcca2bd99d60 (diff) | |
| download | postgresql-8ae4ef4fb0e0331f02c4615182600546c8e5c4d4.tar.gz postgresql-8ae4ef4fb0e0331f02c4615182600546c8e5c4d4.zip | |
Remove incorrect assertion in reorderbuffer.c.
We start recording changes in ReorderBufferTXN even before we reach
SNAPBUILD_CONSISTENT state so that if the commit is encountered after
reaching that we should be able to send the changes of the entire transaction.
Now, while recording changes if the reorder buffer memory has exceeded
logical_decoding_work_mem then we can start streaming if it is allowed and
we haven't yet streamed that data. However, we must not allow streaming to
start unless the snapshot has reached SNAPBUILD_CONSISTENT state.
In passing, improve the comments atop ReorderBufferResetTXN to mention the
case when we need to continue streaming after getting an error.
Author: Amit Kapila
Reviewed-by: Dilip Kumar
Discussion: https://postgr.es/m/CAA4eK1KoOH0byboyYY40NBcC7Fe812trwTa+WY3jQF7WQWZbQg@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions