We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
CDC is preventing the PosgreSQL database source to delete its wals files. From what I see, CDC uses logical replication slots but it never seems to update the value of LSN (Log Sequence Number) : it always points to the wal that was current when the agent was created.
CDC must be able to manage itself the replication slot's LSN position. CDC DB2 z/OS does it natively so with PostgreSQL, it must do the same thing. With a database that produces 500 MB of wal files a day, it is not possible to schedule regular stop subscription/dmsetpostgresqlflushlsn/start subscriptions jobs only because CDC does not do it natively
Do not place IBM confidential, company confidential, or personal information into any field.