Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WYSLG-0001Wp-0F for pgsql-docs@arkaria.postgresql.org; Fri, 11 Apr 2014 03:41:26 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WYSLF-0000VA-CR for pgsql-docs@arkaria.postgresql.org; Fri, 11 Apr 2014 03:41:25 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WYSLC-0000Uo-LU; Fri, 11 Apr 2014 03:41:22 +0000 Received: from mail-ob0-x233.google.com ([2607:f8b0:4003:c01::233]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WYSL5-0004iB-8g; Fri, 11 Apr 2014 03:41:21 +0000 Received: by mail-ob0-f179.google.com with SMTP id va2so5512349obc.10 for ; Thu, 10 Apr 2014 20:41:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5pi4psMDhFh6xMGSSNhHDqMfYwg/KObSt590Jl1J4JQ=; b=TzEwV7deurehNN2F25aZRGbW3EyTenHcg0q1LXsjmfn+poJl8og/IFkE/6DlKvQypY HE77NEtI5SZbJRoHf0NULp2K5g5JwSE3hGZkpSS6F4m+RIuK97pcPbHTdu/vp+bziZ7S sc30i1idoRvYjCPciNTYnphdCNsMsFZ3YFeBVJ7MsFJG876+i2RgFcHYDOMQFe0Wk6iy aFTbW/MD6zK3ZDk6h3soSfxgTOzYEKBklG7jR6cxnevYHN6h25tmOLGBknjvB+RleeTH vlsfPUHUR4ksyKQPPG2tQccCs8Nn0U7ezPM5dQctsj+UrrKizdOEgdQbF+ty0/3l1DVV 1JSw== X-Received: by 10.182.28.195 with SMTP id d3mr17540288obh.19.1397187673397; Thu, 10 Apr 2014 20:41:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.169.98 with HTTP; Thu, 10 Apr 2014 20:40:53 -0700 (PDT) In-Reply-To: <20140411025247.GC5822@eldon.alvh.no-ip.org> References: <7745EA48-8184-4C54-99B6-837D109C7DD5@gmail.com> <20140411025247.GC5822@eldon.alvh.no-ip.org> From: Amit Langote Date: Fri, 11 Apr 2014 12:40:53 +0900 Message-ID: Subject: Re: [GENERAL] About upgrading a (tuple?) lock in a rollback'd sub-transaction To: Alvaro Herrera Cc: Rob Sargent , Postgres General , "pgsql-docs@postgresql.org" Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -1.8 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Fri, Apr 11, 2014 at 11:52 AM, Alvaro Herrera wrote: > Amit Langote wrote: >> On Thu, Apr 10, 2014 at 10:25 PM, Rob Sargent wrote: >> > And it also tells you how to stop it --bibtex iirc >> >> Yeah, it's a caution against a potentially harmful usage anyway. Users >> should not use it at all. >> >> I was just wondering if the description of the behavior, that is, >> potential disappearance of certain locks is complete enough. > > You do realize that this is no longer the case in 9.3, right? > I don't see a point in changing old releases' documentation. I see, okay. And yes, I'm aware that this's no longer an issue in 9.3. Thanks, Amit -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs