forked from postgres/postgres
-
Notifications
You must be signed in to change notification settings - Fork 1
Publication where clause #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ololobus
wants to merge
13
commits into
master
Choose a base branch
from
logical-where-new
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e7daec6
to
d5020cb
Compare
Since commit 7c4f524, atttypmod was added but not used. The removal is safe because COPY from publisher does not need such information.
It seems to be a useful information while allocating memory for queries that returns more than one row. It reduces memory allocation for initial table synchronization. While in it, since we have the number of columns, allocate only nfields for cstrs instead of MaxTupleAttributeNumber.
Relation localrel is the only LogicalRepRelMapEntry structure member that is useful for create_estate_for_relation.
A WHERE clause will be used for row filtering in logical replication. We already have a similar node: 'WHERE (condition here)'. Let's rename the node to a generic name and use it for row filtering too.
When you define or modify a publication you optionally can filter rows to be published using a WHERE condition. This condition is any expression that evaluates to boolean. Only those rows that satisfy the WHERE condition will be sent to subscribers.
263315a
to
65588ab
Compare
55a0b62
to
204a08d
Compare
4d92c23
to
8ad991f
Compare
5a2ad68
to
898c322
Compare
4c121b5
to
2f0b4de
Compare
8542a98
to
2603ea1
Compare
7c657da
to
0e5f4f7
Compare
28db880
to
7f8e356
Compare
b32538b
to
fb6f525
Compare
5d7849e
to
afd25cc
Compare
2843bba
to
9fcc5b8
Compare
7fb7114
to
9dd5d33
Compare
2435350
to
5a0dfc6
Compare
5a5411e
to
63ab42a
Compare
2943f01
to
c87ec8b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.