Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cQDlT-0006d4-HK for pgadmin-hackers@arkaria.postgresql.org; Sun, 08 Jan 2017 13:44:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cQDlS-0004KP-KM for pgadmin-hackers@arkaria.postgresql.org; Sun, 08 Jan 2017 13:44:02 +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 1cQDlF-00045W-1l for pgadmin-hackers@postgresql.org; Sun, 08 Jan 2017 13:43:49 +0000 Received: from mail-it0-x22e.google.com ([2607:f8b0:4001:c0b::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cQDl6-0001iQ-CO for pgadmin-hackers@postgresql.org; Sun, 08 Jan 2017 13:43:48 +0000 Received: by mail-it0-x22e.google.com with SMTP id c20so40170499itb.0 for ; Sun, 08 Jan 2017 05:43:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1bDQRMI7pthrVuRtfyK4TwZTqSwjpEUBXxtCuig236Y=; b=J59wHCA/RCir6KlwdZ1mADfq6HPfM0ktEfEI+csM3WEbwDLvZZpLp4UqWwnKIe3mjb Ev2VBCFoHhSPpNskUkG1VjmMkKQ2JmMNNWFT2akiC90ond539cHhOVSak0whJR8aAkh3 EQxUt9W3jRIciJNhMnJDuzDsRSEHazaGUEWkNGhJRtKbzp/LfXC6KOgovKPKrKwSxHS3 h2t3JDnjMcYVv4g7li1w1bpyTaGW5XxB52e2d6WKCKSu0/3B4tilOPyg1gcYvU5UlExJ 28Hyq7QekIRil2Q9PHlnns44mqCmR+M6BhUDiyJi16jTZiSZfEMadEKyQl2I6uHpqJi8 Gbtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1bDQRMI7pthrVuRtfyK4TwZTqSwjpEUBXxtCuig236Y=; b=EGqmiwZa8AlL0PkmYBQDMG7kuYvrJT6zb43GEJdgj4sn7gxu2dfxbrGVHI5O2AuujV K+2U2eyjhvXdzX4eEXENE+GcSSp5qZ3XMtzlrILToG8o+p4T08kMPEPSK1JflWQjxj64 Y52qM5NM5q3PzdpGPZ79kdvS31nwq2dOBJUNkRsK/WX0NnTUZ+gVz455I/8zh8ewNJ7w rC+ZEV6uqbwlLI6Gsr8gBBzJPTOLPZsWQ0MXDp1jgVre/pi38Z8R/QsVrAapNy9033bB FeQEUXKBBF3qLTpg9Kqoj6c2WVG6qUekLsa3Rnu2GX1LCUyvJSPoRWHcV1dDLM2PFBHg gZ0Q== X-Gm-Message-State: AIkVDXIhCKf/B9wieBRIv17V7fsQI7fKgi17o2fa2k5qvKdtlho1QOTvNnoJ55WKJmsxin28Y73RFu1VWaOvjg== X-Received: by 10.36.175.83 with SMTP id l19mr5854727iti.113.1483883018005; Sun, 08 Jan 2017 05:43:38 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.224.198 with HTTP; Sun, 8 Jan 2017 05:43:37 -0800 (PST) In-Reply-To: References: From: Dave Page Date: Sun, 8 Jan 2017 13:43:37 +0000 Message-ID: Subject: Re: PATCH: To fix the issue in exclusion constraint (pgAdmin4) To: Murtuza Zabuawala Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary=f403045dadc62d6399054595707c X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --f403045dadc62d6399054595707c Content-Type: text/plain; charset=UTF-8 Hi On Friday, December 30, 2016, Murtuza Zabuawala < murtuza.zabuawala@enterprisedb.com> wrote: > Hi, > > PFA patch to fix the issue where we were fetching wrong OID while > generating node which was causing "index out of range". error when user > try to access that exclusion constraint . > RM#1896 > I can't reproduce this, even following the steps in the ticket. How did you manage to reproduce it? -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --f403045dadc62d6399054595707c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi

On Friday, December 30, 2016, Murtuza Zabuawala <murtuza.zabuawala@enterprisedb.com= > wrote:
Hi,
=
PFA patch to fix the issue where we were fetching wrong OID = while generating node which was causing=C2=A0"index out of rang= e".=C2=A0error when user try to access that exclusion constrain= t=C2=A0.
RM#1896

I ca= n't reproduce this, even following the steps in the ticket. How did you= manage to reproduce it?


--
Dave Page
Blog: http://pgsnake.blogspot.com<= /a>
Twitter: @pgsnake

EnterpriseDB UK:
http://www.enterprisedb.com
The Ente= rprise PostgreSQL Company

--f403045dadc62d6399054595707c--