Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iq0tO-0004co-5u for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Jan 2020 20:28:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iq0tM-00023F-TZ for pgsql-bugs@arkaria.postgresql.org; Fri, 10 Jan 2020 20:28:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iq0tM-000238-G6 for pgsql-bugs@lists.postgresql.org; Fri, 10 Jan 2020 20:28:24 +0000 Received: from mail-wr1-x442.google.com ([2a00:1450:4864:20::442]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iq0tJ-00059V-NQ for pgsql-bugs@lists.postgresql.org; Fri, 10 Jan 2020 20:28:23 +0000 Received: by mail-wr1-x442.google.com with SMTP id z3so3020272wru.3 for ; Fri, 10 Jan 2020 12:28:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=A0buA9KdWLk7yAiqhXcTy2i4OrKgvx5ZsWgqn3TiKd8=; b=n8rwTxCFeK/Er1cb3rGVB9EwMdIA3OKxlgNIMpE6fpTuwpyzNvxa+JL1iNV4jMbfhY ITD0wi7VhHQdBCXIiRfRZ0ai6U14glGPzjYwQW5VIwrL3YGHpVXUls7Zv8pG0DS9fys1 6uvmSrD9WAjh4g/YWmAJKy3X53uaLlblRd+qgi/3bHN8bBJU46yQkvj8D8CcgeqyN+mZ YnxVlWtvAd8cqO5wZkpK9eEmQlWEnngJtBGPGa+faATHuIpRx6BuJkSLZknXgDOrnh0Q qk4v64+SgpLCGOIfSzvq1A0YFlQbu7RhQCfeIJz2cT6MbT/X9CKPbsKN5dXJrLMLw1xY YxXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=A0buA9KdWLk7yAiqhXcTy2i4OrKgvx5ZsWgqn3TiKd8=; b=MPvG7S7rHNI0O7srcsOWPku4kBGj4duDHh8cXoj5nIA5EXwuN1qNAWFVrr2lay0Kfg WIM8GPU3UZm1Ih9ZN5B/Hynoh25TVLXRtz70wTK0Gf5m+3LDT6APnieNfzRDXjt7x1ri Ki7LToX418sPH+s/YUq6DtdHH/ViKQgq1cOKMLVKeZ1bgC5IanGIVpmNVX4bMG7oA2jc DzR8ZQhf4sx7MyzmgVwY0DE4XBsD42Crmaz7zwjMbLFqRlK+HimZS8pje/LCt5dZz5K6 ch1oYjycetGMEB//e8v4HxMvpAxl7rUtf5yPC855Kf+sgX9eLd7SPhwioooAkdCsSOfp Hg7w== X-Gm-Message-State: APjAAAWMjMU6UcGDiHW8M0ZWr2fAGfh1zbjqJTH7YNvpVKTTDlx9QQ0l iTdF4iEIprxig/jchQiAcMhFQA== X-Google-Smtp-Source: APXvYqwvkPL/3L746tth7I2dmmEX9NsksolssFinK6EZ1HUq8Im/ttVMMIJc2+wlyCZZ085FzoPMcw== X-Received: by 2002:adf:ee82:: with SMTP id b2mr5490974wro.194.1578688100131; Fri, 10 Jan 2020 12:28:20 -0800 (PST) Received: from localhost (ip-86-49-253-92.net.upcbroadband.cz. [86.49.253.92]) by smtp.gmail.com with ESMTPSA id y139sm3678832wmd.24.2020.01.10.12.28.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Jan 2020 12:28:19 -0800 (PST) Date: Fri, 10 Jan 2020 21:28:18 +0100 From: Tomas Vondra To: remabarca@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16203: So difficult to set an use postgres Message-ID: <20200110202818.mvgvbfnlgfz4bbsy@development> References: <16203-d9b2e0874d6ca215@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <16203-d9b2e0874d6ca215@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Jan 10, 2020 at 07:38:21PM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16203 >Logged by: Reyna Melara >Email address: remabarca@gmail.com >PostgreSQL version: 11.0 >Operating system: Debian Jessie >Description: > >Hi, I've trying for several hours to set, configure and use postgres in >any of my debian operating systems. It seems it has been installed >properly but then when I wanted to use PgAdmin it keep telling me it >could not establish the connection, in my laptop also with debian it >was not possible to use any pgAdmin not 3 nor 4. I have followed the >instructions form the official page and t possible. > >Now that In my PC could finally use postgres and also pgAdmin I can't >use unqualified names, I have to use the public schema or my own >schemas with qualified names, I have also followed the manual >instructions and it it not possible, it keep telling me that my >relations does not exists. Maybe the instructions are for so much more >specialized users, but I can tell that there is a big group of students >that sometimes can't find the instructions easy, specially when we are >not Windows users. > I'm sure improvements to our docs are possible, but I very much doubt a vague report like this qualifies as a bug. It's really difficult to give you any advice if you don't tell us what exactly have you been doing - which packages have you installed, what commands have you tried running, which instructions have you been following, what error messages you got, etc. I'd suggest subscribing to pgsql-general and asking questions there, there's plenty of users who'll happily help you. And of course, if you have concrete examples of parts of the documentation that are not detailed enough, please point them out and we'll try improving them. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services