[BUGS] Problem With Case Statement and Aggregate Functions

The following works as expected: select (SELECT CASE WHEN (1=2) THEN 0 ELSE sum(count) END) from ( select 1 as count union select 2 union select 3 ) as "temp"; The result is "6". The following also works as expected: select count(*) from ( select 1 as count union select 2 union select 3 ) as "

[BUGS] BUG #3267: Relfilenode

The following bug has been logged online: Bug reference: 3267 Logged by: Shyam Sunder Rai Email address: [EMAIL PROTECTED] PostgreSQL version: GreenplumDB Operating system: CentOS Description:Relfilenode Details: I am using our database that is based on Postgres 8.

Re: [BUGS] Problem With Case Statement and Aggregate Functions

On Fri, 11 May 2007 14:47:04 +1000, Andrew Shea <[EMAIL PROTECTED]> wrote: > The following works as expected: > > select (SELECT CASE WHEN (1=2) THEN 0 ELSE sum(count) END) from ( > select 1 as count union select 2 union select 3 > ) as "temp"; > > The result is "6". > > The following also work

Re: [BUGS] Is PostgresSQL supported in Windows Vista?

Jack Ho wrote: > Dear sir, > > Is PostgreSQL supported in Vista? If it is, what version is supported? > IIRC, all windows versions (which means 8.2 really - 8.0 and 8.1 have other problems) work fine on vista *except* that the installation program doesn't properly work. You can install it

Re: [BUGS] BUG #3267: Relfilenode

Shyam Sunder Rai wrote: I am using our database that is based on Postgres 8.1.6. and it even supports clustering on linux machines. I am curious to know the relation between "relfilenode" and Query Executor. This mailing list and form is for PostgreSQL bug reports only. Please address any que

Re: [BUGS] BUG #3267: Relfilenode

Shyam Sunder Rai wrote: The following bug has been logged online: Bug reference: 3267 Logged by: Shyam Sunder Rai Email address: [EMAIL PROTECTED] PostgreSQL version: GreenplumDB if you are using greenplumDB you should ask the greenplum support for help ... Operating sys

[BUGS] BUG #3268: pgpass.conf error

The following bug has been logged online: Bug reference: 3268 Logged by: Nilay Ceter Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.3-1 Operating system: windows XP Description:pgpass.conf error Details: I have been working with postgresql for our project

Re: [BUGS] Problem With Case Statement and Aggregate Functions

Andrew Shea <[EMAIL PROTECTED]> writes: > However the following code doesn't work even though it is very similar > to the first query (that is, and aggregate function within a case > statement): > select (SELECT CASE WHEN (1=2) THEN 0 ELSE COUNT(*) END) from ( ^^ > select 1 as cou

[BUGS] BUG #3269: PSQL does not display error output

The following bug has been logged online: Bug reference: 3269 Logged by: Bojan Jovanovic Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: RHEL3 Description:PSQL does not display error output Details: Hello, We just upgraded to 8.2.4, and

Re: [BUGS] BUG #3269: PSQL does not display error output

"Bojan Jovanovic" <[EMAIL PROTECTED]> writes: > We just upgraded to 8.2.4, and noticed that psql does not display error > messages, e.g.: Works for me. Maybe you have client_min_messages set to a silly value? Or stderr directed away from the terminal? regards, tom lane -

Re: [BUGS] BUG #3269: PSQL does not display error output

On Fri, May 11, 2007 at 01:06:02PM +, Bojan Jovanovic wrote: > We just upgraded to 8.2.4, and noticed that psql does not display error > messages, e.g.: [...] > shp_production=# select * from asdfafsdf; > shp_production=# commit; > ROLLBACK What's the output of "show client_min_messages"? --

[BUGS] BUG #3270: limit < 16 optimizer behaviour

The following bug has been logged online: Bug reference: 3270 Logged by: Liviu Ionescu Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: Linux Description:limit < 16 optimizer behaviour Details: I have a table of about 15Mrows, and a query

Re: [BUGS] BUG #3269: PSQL does not display error output

Here it is... Did not change anything from the default installation - just compiled it, and installed.. shp_production=# show client_min_messages shp_production-# ; client_min_messages - notice (1 row) shp_production=# Is this correct? How would STDERR get redirected fro

Re: [BUGS] BUG #3271: PREPARE/EXCUTE don't work

laurent faillie wrote: While trying to use Apache 2.2 database authentication, I discovered that I wasn't able to retrieve users. After some investigation, I found that PREPARE/EXECUTE are faulty. It can be reproduced in psql as bellow : www=> PREPARE authn_dbd_1 (varchar) AS select mdp from mar

[BUGS] BUG #3271: PREPARE/EXCUTE don't work

The following bug has been logged online: Bug reference: 3271 Logged by: laurent faillie Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.4 Operating system: HP-UX 11.11 (v32 bits). Description:PREPARE/EXCUTE don't work Details: Hi all, While trying to use

Re: [BUGS] BUG #3270: limit < 16 optimizer behaviour

This should have been asked on the performance list, not filed as a bug. I doubt anyone will have a complete answer to your question without EXPLAIN ANALYZE output from the query. Have you ANALYZE'd the tables recently? Poor statistics is one possible cause of the issue you are having. On Fri, Ma

Re: [BUGS] BUG #3269: PSQL does not display error output

Bojan Jovanovic <[EMAIL PROTECTED]> writes: > How would STDERR get redirected from psql? The usual way, like "psql 2>/dev/null", but if you didn't know that then it's unlikely you did it. I have seen symptoms roughly like this one with really ancient SELinux policies (the first draft of the polic

Re: [BUGS] Removing pg_auth_members.grantor (was Grantor name gets lost when grantor role dropped)

So the discussion died again with nothing being decided. I see we have several choices: 1. implement the standard, per Russell suggestion below 2. decide that the standard is braindead and just omit dumping the grantor when it's no longer available, but don't remove pg_auth_members.grantor