Horton

Re: COPY, lock release and MVCC

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2020-05-15T04:41:12Z
Lists: pgsql-hackers 
On Thu, May 14, 2020 at 7:10 PM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> 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.
>

Okay, changed, and pushed.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Commits

  1. Make COPY TO keep locks until the transaction end.

  2. COPY to a relation should keep write lock till transaction commit.

  3. Mega-commit to make heap_open/heap_openr/heap_close take an