** Description changed:

  Binary package hint: php5
  
  A connect failure in pg_connect() or an error in pg_query() will result
  in php exiting after printing a WARNING instead of continuing execution.
  
  I have attached a test script that tries to connect to a non-existent DB
  - on Debian Lenny prints an error correctly:
  
  $ php test.php
  Warning: pg_connect(): Unable to connect to PostgreSQL server: FATAL: 
database "mary" does not exist in /home/mattc/test.php on line 3
  Connection Failure
  
- 
  But on Maverick simply dies after the pg_connect() failure - note that
  "Connection Failure" is not printed:
  
- $ php test.php 
+ $ php test.php
  Warning: pg_connect(): Unable to connect to PostgreSQL server: FATAL:  
database "mary" does not exist
-  in /home/mattc/test.php on line 3
- 
+  in /home/mattc/test.php on line 3
  
  This looks like a related upstream bug:
  
  http://bugs.php.net/bug.php?id=52682
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: php5-pgsql 5.3.3-1ubuntu9
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: ksplice_r5fvn98f ksplice_vx7641xl 
ksplice_hy9n8rtk_vmlinux_new ksplice_hy9n8rtk ksplice_wwlcxuj6 
ksplice_ndv79lmx_vmlinux_new ksplice_ndv79lmx ksplice_wqjhxpxk_vmlinux_new 
ksplice_wqjhxpxk ksplice_vxxnjbjc ksplice_aoojhvc5_vmlinux_new ksplice_aoojhvc5 
ksplice_csiv07iy_vmlinux_new ksplice_csiv07iy nvidia
  Architecture: i386
  Date: Thu Oct 14 10:23:38 2010
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=en_NZ.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_NZ.UTF-8
+  SHELL=/bin/bash
  SourcePackage: php5
+ 
+ 
+ === Stable Release Update (SRU) information ===
+ 
+ IMPACT
+ 
+ The patch being removed does not fix any reproducible problem, so it
+ really should not have been added in the first place.
+ 
+ DEV BRANCH
+ 
+ Natty is not open yet.
+ 
+ PATCH
+ 
+ See associated merge proposal
+ 
+ TEST CASE:
+ 
+ The php script labeled "Test script" attached to this bug reproduces the
+ problem exactly. If the string "Connection Failure" is not seen after
+ running it, the bug is present.
+ 
+ REGRESSION POTENTIAL
+ 
+ If we did fix the pgsql segfaulting problem reported in
+ 
+ https://bugs.launchpad.net/ubuntu/+source/php5/+bug/607646
+ 
+ It will return. However, that bug was never actually confirmed by users,
+ and so I think the potential is "VERY LOW"

-- 
php5-pgsql crash on getting an error back from postgres
https://bugs.launchpad.net/bugs/660227
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to