Re: COPY, lock release and MVCC

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY, lock release and MVCC
Date: 2020-05-14 13:40:44
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, 2020-05-14 at 15:11 +0530, Amit Kapila wrote:
> LGTM. I have slightly modified the commit message, see if that looks
> fine to you.

Fine with me, thanks.

> This breaks the cases where a REPEATABLE READ transaction could see an
> empty table if it repeats a COPY statement and somebody truncated the
> table in the meantime.

I would use "case" rather than "cases" here.

Laurenz Albe

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2020-05-14 15:35:03 Re: new heapcheck contrib module
Previous Message Daniel Gustafsson 2020-05-14 13:03:41 Potentially misleading name of libpq pass phrase hook