[BUGS] BUG #4272: No password can CREATE & DROP database!!

2008-06-29 Thread y.y.chen

The following bug has been logged online:

Bug reference:  4272
Logged by:  y.y.chen
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.2 & 8.3
Operating system:   Server Fedora3  ,client WIN-XP
Description:No password can CREATE & DROP database!!
Details: 

I can execute command "dropdb database and createdb database" without any
password  in WIN-XP text mode  after PgAdminIII 1.8.x had saved connection
USER and PASSWORD!;

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #5414: pg_dump failure from database 8.4.3 to 8.4.3

2010-04-12 Thread y.y.chen

The following bug has been logged online:

Bug reference:  5414
Logged by:  y.y.chen
Email address:  yyc...@clhs.tyc.edu.tw
PostgreSQL version: 8.4.3
Operating system:   XP  and  openSuSE 11.1
Description:pg_dump  failure  from database 8.4.3 to 8.4.3
Details: 

pg_dump execute failure at dump from host to other host down in  all OS!

pg_dump from 8.4.2 to 8.4.3 is OK!
But pg_dump from 8.4.3 to 8.4.3 alway be failure!
My SQL struction is 
"pg_dump -h192.168.0.17 -O db |psql -p5432 db "

It can not do finished , It will be down !

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #5432: pg_dump (8.4.3) copy database failure!

2010-04-21 Thread y.y.Chen

The following bug has been logged online:

Bug reference:  5432
Logged by:  y.y.Chen
Email address:  yyc...@clhs.tyc.edu.tw
PostgreSQL version: 8.4.3
Operating system:   OpenSuSE  and XP
Description:pg_dump (8.4.3)  copy database  failure!
Details: 

Server A:Ver 8.4.3  
Server B:Ver 8.4.2 

pg_dump in A=> pg_dump -h A  db > file  =>failure
pg_dump inB => pg_dump -h A  db > file  =>success

While dump failure and pg_dump can't run to over !
It's possible then  pg_dump fail at field with character varying(480)!

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #5433: pg_dump (8.4.3) copy database failure!

2010-04-21 Thread y.y.Chen

The following bug has been logged online:

Bug reference:  5433
Logged by:  y.y.Chen
Email address:  yyc...@clhs.tyc.edu.tw
PostgreSQL version: 8.4.3
Operating system:   OpenSuSE  and XP
Description:pg_dump (8.4.3)  copy database  failure!
Details: 

Server A:Ver 8.4.3  
Server B:Ver 8.4.2 

pg_dump in A=> pg_dump -h A  db > file  =>failure
pg_dump in B => pg_dump -h A  db > file  =>success

While dump failure and pg_dump can't run to over !
It's possible then  pg_dump fail at field with character varying(480)!

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #5576: Boolean operation should not be Complete boolean evaluation

2010-07-29 Thread y.y.chen

The following bug has been logged online:

Bug reference:  5576
Logged by:  y.y.chen
Email address:  segma.yyc...@msa.hinet.net
PostgreSQL version: 8.4.x
Operating system:   WINDOWS-XP
Description:Boolean operation should not  be Complete boolean
evaluation
Details: 

When I run SQL -scripts in trigger/PlpgSQL:

IF (TG_OP = 'INSERT') OR (old.size<>new.size) THEN
...
END IF;

 It raise a exception: RECORD old never be defined,
 while TG_OP is 'INSERT'.



It is happen in 8.3.11,8.4.1~8.4.4-1
But 9.0.0.beta 3 is OK!

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs


[BUGS] BUG #5577: Boolean operation should not be Complete boolean evaluation

2010-07-29 Thread y.y.chen

The following bug has been logged online:

Bug reference:  5577
Logged by:  y.y.chen
Email address:  yyc...@mail.clhs.tyc.edu.tw
PostgreSQL version: 8.4.x
Operating system:   WINDOWS-XP
Description:Boolean operation should not  be Complete boolean
evaluation
Details: 

It's happen in version 8.3.11,8.4.1,8.4.4
but not in 9.0.0.beta3.

When I run in PlpgSQL /Trigger :

IF ( TG_OP = 'INSERT') OR (old.size<>new.size) then

END IF;

While TG_OP is 'INSERT' and then raise a exception
 RECORD old never be defined !

It's not an efficiency SQL-scripts for "Complete boolean evaluation "!

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs