Thread: BUG #16203: So difficult to set an use postgres

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.

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 

Reyna Melara <remabarca@gmail.com> writes:
> I understand I need to be more specific, I have

> Admissions=# \dt
>         Listado de relaciones
>  Esquema | Nombre  | Tipo  |  Dueño
> ---------+---------+-------+----------
>  public  | apply   | tabla | postgres
>  public  | college | tabla | postgres
>  public  | student | tabla | postgres
> (3 filas)

> SELECT sID, sName, GPA FROM Student WHERE GPA > 3.6;
> ERROR:  no existe la relación «student»
> LÍNEA 1: SELECT sID, sName, GPA FROM Student WHERE GPA > 3.6;

It's pretty hard to make those two observations match up.
The "\dt" command shows that you have a table named "student",
and that that's in the "public" schema, and that "public" is
in your search_path (else \dt wouldn't have shown it).
But then the query isn't finding the table.  That certainly
seems impossible if you had issued the query through psql
in the same session where you did the "\dt", so I assume that
you are issuing the query in some other way that you're not
telling us about.  It's tough to give useful advice when we're
not seeing the real picture.

> and I have read it may be because of the Schema Search Path as
> https://www.postgresql.org/docs/9.1/ddl-schemas.html documents.

Well, that's a possible answer, but "public" is in the search
path by default so I don't think it's the most likely answer.

What I think is a more likely answer is that your query is being
issued in some other database than the one you did the "\dt"
command in.  Check the connection parameters for whatever you're
using to issue the query.

Also, I notice that above you are connected to a database named
"Admissions" (with a capital A).  I wonder if you are managing
to confuse yourself with mixed-case names.  Try "\l" in psql
and see if you also have a database named "admissions" (lower
case); if so, maybe your query is being issued in that one?

            regards, tom lane