Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1iGEUd-0005wH-0j
	for pgsql-bugs@arkaria.postgresql.org; Fri, 04 Oct 2019 03:42:59 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1iGEUa-0000HG-BU
	for pgsql-bugs@arkaria.postgresql.org; Fri, 04 Oct 2019 03:42:56 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1iGEUa-0000H8-3z
	for pgsql-bugs@lists.postgresql.org; Fri, 04 Oct 2019 03:42:56 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1iGEUT-0001en-Ma
	for pgsql-bugs@lists.postgresql.org; Fri, 04 Oct 2019 03:42:55 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x943gh8x012362;
	Thu, 3 Oct 2019 23:42:43 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: =?utf-8?B?0JDQvdGC0L7QvSDQktC70LDRgdC+0LI=?= <druidvav@gmail.com>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16036: Segmentation fault while doing an update
In-reply-to: <20191004033610.fb47ehgycodogn6w@alap3.anarazel.de>
References: <16036-28184c90d952fb7f@postgresql.org>
 <4E1FB33C-7280-487B-B3D1-D3C247AA9E3D@anarazel.de>
 <FBA5344D-9356-49BA-9B47-C3705C2E9481@gmail.com>
 <A1695349-530C-4871-AED5-0262A9BC9920@anarazel.de>
 <746398E3-F4E1-4F14-A686-3394F27011DC@gmail.com>
 <20191004032020.se46diwqas43e3tw@alap3.anarazel.de>
 <11540.1570159561@sss.pgh.pa.us>
 <20191004033610.fb47ehgycodogn6w@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Thu, 03 Oct 2019 20:36:10 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12360.1570160563.1@sss.pgh.pa.us>
Date: Thu, 03 Oct 2019 23:42:43 -0400
Message-ID: <12361.1570160563@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
> Yea, I was wondering about that too - but asking for a slot to be copied
> into itself seems to indicate a logic bug more often than not? Expecting
> the slots to be independent, afterwards. So I'm a bit hesitant doing so.

Oh, good point.  The Assert sounds better then.

			regards, tom lane