Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bMwR0-0004jz-2K for pgadmin-hackers@arkaria.postgresql.org; Tue, 12 Jul 2016 12:05:06 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bMwQz-0002WH-GY for pgadmin-hackers@arkaria.postgresql.org; Tue, 12 Jul 2016 12:05:05 +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 1bMwQm-00023U-9N for pgadmin-hackers@postgresql.org; Tue, 12 Jul 2016 12:04:52 +0000 Received: from mail-io0-x22a.google.com ([2607:f8b0:4001:c06::22a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bMwQi-0008SP-KS for pgadmin-hackers@postgresql.org; Tue, 12 Jul 2016 12:04:51 +0000 Received: by mail-io0-x22a.google.com with SMTP id m101so14083842ioi.2 for ; Tue, 12 Jul 2016 05:04:48 -0700 (PDT) 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=BDE9Ai6ybJ5/R89erzn+yrChOZJJoG24cQZTeIPWddw=; b=PWKgDWD1v0uSiH9hf25GRfbf1UHB+eo0qBMBT7qyddaH/1U6oLtJ+vpzU8tEiMJOeF TSCrpqlR1tAjdt3SV8FUvi0RKignYq16PXztc7Sii7D4mRnxk9wFvFvelzKK8RTL8+P3 ZS6ag+yrp7/dJXMmapmamJ8Byskf46dtJQ5s1uu4NlcM/1TwBYMfYlnQ6RPQG3V1nJu2 kxG8cAdjHcceuPgqecx1TmkWngNCSHyV15XIqu1Rdow9OtgrBg2zCaB4eVhrhDehrmbz IxYWNAyZR6Xh0/cKbe8T8Y43li13rJLBjJkt1QQFd9JxWXfPAk6j3KHY4YoJYbI1pGHJ Rk6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BDE9Ai6ybJ5/R89erzn+yrChOZJJoG24cQZTeIPWddw=; b=HSm3/XygLzwlW/MZoYA6be7ojrhAEjT++Q0MkfKNw9wxRZuiPFw1uUHV/+UemC5HJt NjdTPyv+h8IFifs5+sO1EfzIehH2U/439zgb6l/Pww39PmDHLmUt4049Zh7jQ3sXvl4D jpk6VNl5uNE/ZQS+LULyH0arJkiIQnS/9D4q8+g/wYctJD710So0wGzXtdsiPECUUZsA F2Dl6b92keK1k4W8RvOLgdQZaT0MbsoN2ZX0hXMZZkK2UVODQfhvCkX5ioJj7H4Zn/5D Sc45p6zvmlAWq/yEMsWHLqWeSYC48f8q5jSBp5hZ3nnC3nZk0z4BKVK8Awy6V851lzDK sECw== X-Gm-Message-State: ALyK8tJTfZ24Ft7G0Ef6nOB9kxqxnEGhhO5/Tx3pJ7pAIcJ7M9+kznuWa9fOP8BGYHKkuqBd2c67RKEIzI9F6w== X-Received: by 10.107.183.85 with SMTP id h82mr2433036iof.63.1468325086850; Tue, 12 Jul 2016 05:04:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.208.97 with HTTP; Tue, 12 Jul 2016 05:04:45 -0700 (PDT) In-Reply-To: References: <1C830532-F2F0-4FBC-BD17-4428CE9AA53D@pgadmin.org> From: Dave Page Date: Tue, 12 Jul 2016 13:04:45 +0100 Message-ID: Subject: Re: pgAdmin IV API test cases patch To: Khushboo Vashi Cc: Priyanka Shendge , pgadmin-hackers , Kanchan Mohitey Content-Type: text/plain; charset=UTF-8 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 On Tue, Jul 12, 2016 at 5:14 AM, Khushboo Vashi wrote: > > > On Mon, Jul 11, 2016 at 7:15 PM, Priyanka Shendge > wrote: >> >> >> >> On 11 July 2016 at 18:35, Dave Page wrote: >>> >>> On Mon, Jul 11, 2016 at 1:25 PM, Priyanka Shendge >>> wrote: >>> > Sorry, by mistake i copied incomplete query. There is an OID present >>> > for >>> > added database. >>> > >>> > SELECT >>> > db.oid as did, db.datname, db.datallowconn, >>> > pg_encoding_to_char(db.encoding) AS serverencoding, >>> > has_database_privilege(db.oid, 'CREATE') as cancreate, >>> > datlastsysoid >>> > FROM >>> > pg_database db >>> > WHERE db.oid = 158579 >>> >>> There's nothing wrong with that query. Can you work with Khushboo to >>> see if she can reproduce or help figure it out please? >> >> >> I had work with Khushboo, she also tried to reproduce the issue at her >> it's working fine for her. >> Khushboo also tried to troubleshoot/trace the issue but not able to figure >> out where exactly its failing; >> as issue was not reproducible. >> >> @Khushboo: >> Please add if i am missing anything. >>> >>> > > > We have tried to reproduce this issue at our end several times with the > different scenarios but every attempt was unsuccessful. > > Here the newly created database connection is failing which should not as > the database is created properly as per the log. > The above query (mentioned by Priyanka) executes from the psycopg2 driver > and could fail in 2 scenarios, either the database has been dropped before > this particular test-case runs or the database is not created properly > through the 'create database test-case'. But as per the log, the 'delete > database test-case' runs after this test-case and the database is created > properly. > > Can any privilege issue prevent the database connection in this scenario? Not on my system, that I can think of. If there was a connection error like that though, shouldn't we see a message from libpq at least? If not, that implies that there are error reporting issues to be fixed. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers