Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE

2017-07-15 Thread Tom Lane
postgre...@get-experience.com writes: > Den 15. juli 2017 23:15, skrev Tom Lane: >> Perhaps you could make your PK be on (id, valid_from, valid_to). > Doesn't really work because valid_to would change on UPDATE. I'd need to > update foreign relations with another trigger which would be very ugly.

Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE

2017-07-15 Thread postgresql
Den 15. juli 2017 23:15, skrev Tom Lane: > postgre...@get-experience.com writes: >> I'm having a problem with the timetravel extension. Following simple schema: >> ... >> What am I doing wrong here? According to the function comment in >> timetravel.c it should: >> a) set last-version row to NEW d

Re: [GENERAL] spi/timetravel: unique constraint violation on UPDATE

2017-07-15 Thread Tom Lane
postgre...@get-experience.com writes: > I'm having a problem with the timetravel extension. Following simple schema: > ... > What am I doing wrong here? According to the function comment in > timetravel.c it should: > a) set last-version row to NEW data; valid_from=now() > b) insert a new row with