Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on May 19, 2022

Poor management of CDC parser on Postgresql timestamp format

Cf CASE TS009333426

PostgreSQL supports the full set of SQL date and time types , shown in this table

Source :


Storage Size


Low Value

High Value


timestamp [ (p) ] [ without time zone ]

8 bytes

both date and time (no time zone)

4713 BC

294276 AD

1 microsecond

timestamp [ (p) ] with time zone

8 bytes

both date and time, with time zone

4713 BC

294276 AD

1 microsecond


4 bytes

date (no time of day)

4713 BC

5874897 AD

1 day

time [ (p) ] [ without time zone ]

8 bytes

time of day (no date)



1 microsecond

time [ (p) ] with time zone

12 bytes

time of day (no date), with time zone



1 microsecond

interval [ fields ] [ (p) ]

16 bytes

time interval

-178000000 years

178000000 years

1 microsecond

The timestamp format permit to have a year greater than 9999 . The Log Parser and CDC protocol dont support year greater than 9999.

our wish is to align the CDC parser with the capabilities of Postgresql

Needed By Month
  • Admin
    Alex Klufas
    Aug 4, 2022

    IBM Update: Thanks for submitting this idea. We've reviewed it and think it is a valid requirement. But at this time, we have not committed to addressing this requirement. We will look for more feedback from users to help us determine if we will prioritize this feature in the future.