postgresqltime-travel

Time Travel functions in postgresql

Can anyone recommend for/against the time-travel functions in postgresql's contrib/spi module? Is there an example available anywhere?

Tnx

Solution

  • The argument for time-travel would be being able to look at tables that are updated often at an earlier insertion/deletion point. Say a table of stock prices for a firms investment portfolio.
    The argument against would be the extra storage space it eats up.

    Here is an Example of use.