Re: COPY, lock release and MVCC

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
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 09:41:34
Message-ID: CAA4eK1JLaoxFQkw6YTr5vMsExD8aY+KVnkocUNLtKskKhr8BAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 14, 2020 at 2:06 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> > I wonder why you have removed (rel != NULL) check?
>
> That was just unexcusable sloppiness, nothing more.
>

LGTM. I have slightly modified the commit message, see if that looks
fine to you.

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

Attachment Content-Type Size
0001-Make-COPY-TO-keep-locks-until-the-transaction-end.v3.patch application/octet-stream 1.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2020-05-14 09:52:10 Re: pgsql: Show opclass and opfamily related information in psql
Previous Message Juan José Santamaría Flecha 2020-05-14 09:12:03 Re: PG compilation error with Visual Studio 2015/2017/2019