On 11/28/2017 04:40 PM, Robert Haas wrote:
> On Sun, Sep 3, 2017 at 5:28 PM, Joe Conway <mail@joeconway.com> wrote:
>> I was playing around with partitioning and found an oddity that is best
>> described with the following reasonably minimal test case:
>
> I can reproduce this without partitioning, just by creating two
> independent tables with the same schema and tweaking a few things from
> your test case to refer to the correct table rather than relying on
> tuple routing:
[snip]
> There's no error here because I didn't bother putting constraints on
> the table, but that tsr = empty bit is still happening. I think the
> problem is that you're updating the same row twice in the same
> transaction, and now() returns the same value both times because
> that's how now() works, so the second time the range ends up with the
> lower and endpoints that are equal.
Yeah, Tom already pointed that out a while back:
https://www.postgresql.org/message-id/20986.1504478066%40sss.pgh.pa.us
FWIW, I have working version of this now (using clock_timestamp()) here
(see last part of the appendix):
https://www.joeconway.com/presentations/SecurePostgreSQL-PGOpen2017.pdf
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
