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.
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
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
Hey,
I'm having a problem with the timetravel extension. Following simple schema:
CREATE EXTENSION timetravel;
CREATE TABLE entries (
id SERIAL NOT NULL,
value INT NOT NULL,
valid_from ABSTIME NOT NULL,
valid_to ABSTIME NOT NULL,
PRIMARY KEY (id, valid_f
While installing Psycopg2 for Python2 in Fedora 26 having Postgresql 9.6:
# dnf install python-psycopg2
Last metadata expiration check: 0:01:52 ago on Sat 15 Jul 2017 08:30:26 AM
-03.
Error:
Problem: conflicting requests
- nothing provides postgresql94-libs needed by
python-psycopg2-2.7.1-1.f26
2017-07-13 20:15 GMT+12:00 Michael Paquier :
> On Thu, Jul 13, 2017 at 5:26 AM, Jeff Janes wrote:
> >
> > I think that none of the recovery information functions
> > (https://www.postgresql.org/docs/9.6/static/functions-
> admin.html#FUNCTIONS-RECOVERY-INFO-TABLE)
> > can distinguish a hot standb