Re: Possible error in psql or Postgres?

From: Dusan Misic <promisic(at)gmail(dot)com>
To: David Johnston <polobo(at)yahoo(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Possible error in psql or Postgres?
Date: 2012-06-12 19:41:04
Message-ID: CAGdZ+NDuQwfDgwoaU71oKrNbLCB0FNAUdbLJp5DCEiT2p7EK=Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12.6.2012 21:33, David Johnston wrote:

On Jun 12, 2012, at 15:21, Dusan Misic <promisic(at)gmail(dot)com> wrote:

Is this normal Postgres / psql behavior?

griffindb=# \d system.user;
Table "system.user"
Column | Type | Modifiers

-----------+-----------------------+--------------------------------------------
--------
username | character varying(20) | not null
password | character varying(32) | not null
firstname | character varying(40) | not null default 'nema ime'::character
vary
ing
lastname | character varying(40) | not null default 'nema
prezime'::character
varying
Indexes:
"SystemUser_PK" PRIMARY KEY, btree (username) CLUSTER

normal query:

griffindb=# select * from system.user where username = 'root';
username | password | firstname | lastname
----------+----------------------------------+-----------+---------------
root | 1e7db545fccbf4e03abc6b71d329ab4f | Super | administrator
(1 row)

error query:

griffindb=# select * from system.user where user = 'root';
username | password | firstname | lastname
----------+----------+-----------+----------
(0 rows)

column user does not exist should throw an error!

PostgreSQL / psql version: 9.1.3 on Windows 7 64-bit

Should Postgres or psql report an error because column used in WHERE clause
does not exist?

http://www.postgresql.org/docs/9.0/interactive/functions-info.html

"user" is actually a function the returns the current_user. It is an SQL
special function and thus does not require the use of () after the function
name. So basically you are saying "where current_user = 'root'" which is
either a constant true or false for the statement.

David J.

Found the problem. Work USER is a reserved word. It is written in
PostgreSQL documentation. Sorry for false alarm. My bad.

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2012-06-12 20:00:45 Re: Restrict ALTER FUNCTION CALLED ON NULL INPUT (was Re: Not quite a security hole: CREATE LANGUAGE for non-superusers)
Previous Message David Johnston 2012-06-12 19:33:52 Re: Possible error in psql or Postgres?