.com> wrote:
> On Friday, July 6, 2018, Brent Kerby wrote:
>
>> Of course if the table has a primary key, then this can be used, but I'm
>> wondering how to handle this in the general case where a primary key might
>> not exist.
>>
>
> Personally, I would
;new_row', each of which have the appropriate record type. In
this way, the old table and new table are essentially "pre-joined" in the
transition table.
Would this be workable? Or is there some other way of achieving this?
- Brent Kerby
The issue is that presence of timestamps is fundamental to the
functionality of temporal tables. The users need to.be able to make queries
on temporal tables in terms of timestamps; LSNs won't mean anything to
them. It would be an option to implement the temporal tables using LSNs
under the hood, b
cking or including anything more in the WAL,
right?
On Tue, Feb 20, 2018 at 11:09 AM, Patrick Krecker
wrote:
> On Tue, Feb 20, 2018 at 9:51 AM, Andres Freund wrote:
> > Hi,
> >
> > Leaving Tom's concerns aside:
> >
> > On 2018-02-19 13:42:31 -0700, Brent Kerby wr
AL
specifically for this, or whether there are already timestamps (e.g., as
part of WAL metadata) that could serve this purpose.
Any thoughts?
- Brent Kerby
