Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bWSRt-0008Oz-8h for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Aug 2016 18:05:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bWSRs-0006tV-OQ for pgsql-hackers@arkaria.postgresql.org; Sun, 07 Aug 2016 18:05:20 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bWSQV-00040D-Pg for pgsql-hackers@postgresql.org; Sun, 07 Aug 2016 18:03:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bWSQT-0003da-Is for pgsql-hackers@postgresql.org; Sun, 07 Aug 2016 18:03:54 +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 u77I3mHc003191; Sun, 7 Aug 2016 14:03:48 -0400 From: Tom Lane To: Robert Haas cc: Andrew Gierth , Amit Kapila , Andreas Seltenreich , pgsql-hackers Subject: Re: [sqlsmith] Crash in GetOldestSnapshot() In-reply-to: References: <87vazemeda.fsf@credativ.de> <874m6ydrna.fsf@news-spur.riddles.org.uk> <87zioqcbbv.fsf@news-spur.riddles.org.uk> Comments: In-reply-to Robert Haas message dated "Sun, 07 Aug 2016 13:58:21 -0400" Date: Sun, 07 Aug 2016 14:03:48 -0400 Message-ID: <3189.1470593028@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Robert Haas writes: > So I think in the short term what we should do about this is just fix > it so it doesn't crash. Well, we clearly need to fix GetOldestSnapshot so it won't crash, but I do not think that having RETURNING queries randomly returning "ERROR: no known snapshots" is acceptable even for a beta release. If we aren't prepared to do something about that before Monday, I think we need to revert 3e2f3c2e until we do have a fix for it. What I suggested just now in <2850.1470592623@sss.pgh.pa.us> might be implementable with a couple hours' work, though. Do you have a reason to think it'd be insufficient? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers