[HACKERS] Possible error in psql or Postgres?
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?
Re: [HACKERS] Possible error in psql or Postgres?
On 12.6.2012 21:33, David Johnston wrote: On Jun 12, 2012, at 15:21, Dusan Misic promi...@gmail.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.
Re: [HACKERS] PostgreSQL Core Team
Congratulations Magnus. On Thu, Apr 28, 2011 at 7:37 AM, Pavel Golub pa...@microolap.com wrote: Hello. Congratulations! You wrote: DP I'm pleased to announce that effective immediately, Magnus Hagander DP will be joining the PostgreSQL Core Team. DP Magnus has been a contributor to PostgreSQL for over 12 years, and DP played a major part in the development and ongoing maintenance of the DP native Windows port, quickly becoming a committer to help with his DP efforts. He's one of the project's webmasters and sysadmins and also DP contributes to related projects such as pgAdmin. In his spare time, he DP serves as President of the Board of PostgreSQL Europe. DP Regards, Dave. DP -- DP Dave Page DP PostgreSQL Core Team DP http://www.postgresql.org/ -- With best wishes, Pavel mailto:pa...@gf.microolap.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Query Optimizer + Parallel Operators
This is kinda scary . Oracle guy asking for PostgreSQL documentation and internals of the optimizer. On Thu, Jan 27, 2011 at 12:14 AM, Josh Berkus j...@agliodbs.com wrote: Felix, I'm interested in the query optimizer of PostgreSQL DB. Where could I find useful documentation or could you send me a pointer in the source code? What kind of parallelism does PostgreSQL use for operators, like selection or join? Normally we're very helpful with this kind of information ... it's all public after all ... but I have to say that the domain you're e-mailing from makes it a little hard to give you a direct answer. Could you maybe give us a little information about what you want this information for? -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
