Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d6b9P-0008Tm-RF for pgsql-hackers@arkaria.postgresql.org; Fri, 05 May 2017 11:11:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d6b9P-0008Uj-Do for pgsql-hackers@arkaria.postgresql.org; Fri, 05 May 2017 11:11:55 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d6b7r-0002yt-2c for pgsql-hackers@postgresql.org; Fri, 05 May 2017 11:10:19 +0000 Received: from mail-wm0-x232.google.com ([2a00:1450:400c:c09::232]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1d6b7n-0001sX-GF for pgsql-hackers@postgresql.org; Fri, 05 May 2017 11:10:18 +0000 Received: by mail-wm0-x232.google.com with SMTP id u65so20699838wmu.1 for ; Fri, 05 May 2017 04:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=xhjOMGmD93yF2V27sNAvjpPwewlMJ3Gu9pXRX/aVII0=; b=teZt3F2sfB3qeX7mhwGCF1A6vAYHZ6UhQJMIpKhgksZp0xuOWOMh7/fNqp/iZJAII8 NtOM6oe+4kG4PCBaE8Y3qO5XA3zQkGrIJxVhskxu4LAMwRTTpv92l+MjduLbOSWfSWct uW+jKwGbgyEYJVQf7022MZd2BGu5hXpoqkth4db3WIFQNFwgU05RYt1Bmjc3XjEFnsQo qApSq1Htkjl3xxknIjrx+WmxsZycoTOAxQYx91e7aVsC0rLsVLQAX8mgETRCflYUdhyQ W/XP4wS2rGSMkEu08bKGym0Wk+HEXu5xm33Got87YcwfFyP2cy5c6tdvD6A8gDnJF2ye R56g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xhjOMGmD93yF2V27sNAvjpPwewlMJ3Gu9pXRX/aVII0=; b=Pex58GBlMy7vF/LCkCbVuBYTsVr8nkfgpvU7ZBwSZPySUDYoYrq3IEJGOwwtwWoENM 3klRSn3w7SqcxiRsXfqkIlN9IDsssiVmlUvGxSUx+Xhvy/2relUnt0iGDR3rseByHZz3 xJmkYs//9zrtS5LefzzP49OBPscTSIibSnR6VNcua5l+oOoo9QVzhm4QTv7fltfvzozy LAWZofX6GDHWWyTjotghNuvfgjO/J8iqiMoRgHUpWfjdnldn0msJSjOkOwz0m0J4fNjl WBsNaE9OhH37B7C1koGVbPxQ4r48irFZM/+oxJUjoPv6BLly5as1jNHyIbeGSBVAShny WFwg== X-Gm-Message-State: AN3rC/7BAV369Xbcm1dUrpljryht3q3tgo0QZvVc9lZCM5+NcTO2ZBKM GZkmv2iL7sA9LgB0 X-Received: by 10.28.173.65 with SMTP id w62mr5161782wme.48.1493982612734; Fri, 05 May 2017 04:10:12 -0700 (PDT) Received: from [192.168.0.105] (150.123.broadband11.iol.cz. [90.178.123.150]) by smtp.gmail.com with ESMTPSA id j44sm3671370wre.67.2017.05.05.04.10.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 05 May 2017 04:10:11 -0700 (PDT) Subject: Re: snapbuild woes To: Andres Freund References: <20170413002959.apytyi5lkknauauj@alap3.anarazel.de> <0d06dfc1-0bc5-c3ab-3555-24e2f275d7fa@2ndquadrant.com> <30242bc6-eca4-b7bb-670e-8d0458753a8c@2ndquadrant.com> <20170501005921.qcqd7w2njpv3av6s@alap3.anarazel.de> <20170501013529.sejtgo2acxbvq26q@alap3.anarazel.de> <209861fc-718f-0a7b-3a1d-36512865c209@2ndquadrant.com> <20170501080348.vb6mj5whdex3f7l7@alap3.anarazel.de> <20170501191419.coqbtx2jodu22ufz@alap3.anarazel.de> <20170505000004.gihrtl7bhxeolf3q@alap3.anarazel.de> Cc: PostgreSQL-development , Erik Rijkers , Robert Haas , Craig Ringer From: Petr Jelinek Message-ID: Date: Fri, 5 May 2017 13:10:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170505000004.gihrtl7bhxeolf3q@alap3.anarazel.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) 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 On 05/05/17 02:00, Andres Freund wrote: > Hi, > > On 2017-05-02 08:55:53 +0200, Petr Jelinek wrote: >> Aah, now I understand we talked about slightly different things, I >> considered the running thing to be first step towards tracking aborted >> txes everywhere. >> I think >> we'll have to revisit tracking of aborted transactions in PG11 then >> though because of the 'snapshot too large' issue when exporting, at >> least I don't see any other way to fix that. > > FWIW, that seems unnecessary - we can just check for that using the > clog. Should be very simple to check for aborted xacts when exporting > the snapshot (like 2 lines + comments). That should address your > concern, right? Right, because there isn't practical difference between running and aborted transaction for us so we don't mind if the abort has happened in the future. Yeah the export code could do the check seems quite simple. -- Petr Jelinek http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers