diff options
author | Peter Eisentraut <peter@eisentraut.org> | 2024-01-26 13:52:05 +0100 |
---|---|---|
committer | Peter Eisentraut <peter@eisentraut.org> | 2024-01-26 13:52:05 +0100 |
commit | f7cf9494bad3aef1b2ba1cd84376a1e71797ac50 (patch) | |
tree | 5b05b764dddbcf8ebe7a52a52df24370c37beae3 /contrib/test_decoding/test_decoding.c | |
parent | 8c9da1441df18bd609f025778e8349873a3e9bbd (diff) | |
download | postgresql-f7cf9494bad3aef1b2ba1cd84376a1e71797ac50.tar.gz postgresql-f7cf9494bad3aef1b2ba1cd84376a1e71797ac50.zip |
Split some code out from MergeAttributes()
- Separate function to merge a child attribute into matching inherited
attribute: The logic to merge a child attribute into matching
inherited attribute in MergeAttribute() is only applicable to
regular inheritance child. The code is isolated and coherent enough
that it can be separated into a function of its own.
- Separate function to merge next parent attribute: Partitions inherit
from only a single parent. The logic to merge an attribute from the
next parent into the corresponding attribute inherited from previous
parents in MergeAttribute() is only applicable to regular
inheritance children. This code is isolated enough that it can be
separate into a function by itself.
These separations makes MergeAttribute() more readable by making it
easier to follow high level logic without getting entangled into
details.
Author: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/52a125e4-ff9a-95f5-9f61-b87cf447e4da@eisentraut.org
Diffstat (limited to 'contrib/test_decoding/test_decoding.c')
0 files changed, 0 insertions, 0 deletions