Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit2d09e44

Browse files
author
Amit Kapila
committed
Improve comments for row filtering and toast interaction in logical replication.
Reported-by: Antonin HouskaAuthor: Amit KapilaReviewed-by: Antonin Houska, Ajin CherianDiscussion:https://postgr.es/m/84638.1649152255@antos
1 parent17a856d commit2d09e44

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

‎src/backend/replication/pgoutput/pgoutput.c

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1237,10 +1237,11 @@ pgoutput_row_filter(Relation relation, TupleTableSlot *old_slot,
12371237
* For inserts, we only have the new tuple.
12381238
*
12391239
* For updates, we can have only a new tuple when none of the replica
1240-
* identity columns changed but we still need to evaluate the row filter
1241-
* for new tuple as the existing values of those columns might not match
1242-
* the filter. Also, users can use constant expressions in the row filter,
1243-
* so we anyway need to evaluate it for the new tuple.
1240+
* identity columns changed and none of those columns have external data
1241+
* but we still need to evaluate the row filter for the new tuple as the
1242+
* existing values of those columns might not match the filter. Also, users
1243+
* can use constant expressions in the row filter, so we anyway need to
1244+
* evaluate it for the new tuple.
12441245
*
12451246
* For deletes, we only have the old tuple.
12461247
*/

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp