Closed KennyChenFight closed 1 year ago
This is really cool! Thanks @KennyChenFight!
BTW, is there any chance to drop the pglogical dependency?
This is really cool! Thanks @KennyChenFight!
BTW, is there any chance to drop the pglogical dependency?
Now, the client has the option to choose which decoder to use. By default, the pglogical decoder is used. However, if the client is using PostgreSQL version 14 or above, they can specify to use the pgoutput decoder instead. In this case, the client does not need to install pglogical in their PostgreSQL. So, we still can keep pglogical decoder implemation in code ?
Sure, we should keep the pglogical implementation. However, I believe making pgoutput as default is better since it lowers the barrier to use this library for new users.
Sure, we should keep the pglogical implementation. However, I believe making pgoutput as default is better since it lowers the barrier to use this library for new users.
Considering that the pgoutput binary format is only supported in PG 14 or above, and PG 14 is still a relatively newer version, it might be better to set the pglogical decoder as the default option. Or, maybe I could implement pgoutput text format ?
It is ok to only support PG 14 and above. I believe there are more people using PG >= 14 than having pglogical installed.
@rueian I think you can start to review my code !
This is a draft version for support pgoutput plugin when pg version >= 14.