The following bug has been logged online:
Bug reference: 5318
Logged by: IP
Email address: ireneusz.pastus...@poczta.fm
PostgreSQL version: 8.4.2
Operating system: Sun Solaris 10 x86
Description:Inconsistent PHP pg_result_error_field
PGSQL_DIAG_SOURCE_FUNCTION across
IP ireneusz.pastus...@poczta.fm writes:
Issue: no value returned for 8.4.2 Solaris 10 x86 installation
This isn't necessarily a bug. The source-function report depends
on having used a C compiler that supports the __func__ or __FUNCTION__
symbol, and not all do. Most likely your Solaris 10
That seems to be the reason. I have just installed 8.4.2 from source using
/usr/sfw/bin/gcc
and the function is working now. The version with function that didn't
return anything was installed from package, so I will try to contact
maintainer - maybe there is a chance this functionality.
The following bug has been logged online:
Bug reference: 5317
Logged by: Marc
Email address: rasck...@gmail.com
PostgreSQL version: 8.4.2-1
Operating system: windows xp
Description:no puedo instalarlo
Details:
No me deja instalar el programa ya que me pide una
Just had a very odd thing happen with an 8.4.2 database, and am
concerned it's an undiagnosed bug:
(1) created and dropped the same database 10-15 times in the course of
running some tests.
(2) at one point, dropdb hung. Indefinitely.
(3) attempts to pg_cancel_backend on the DROP DATABASE
On Fri, Feb 5, 2010 at 6:25 PM, Marc rasck...@gmail.com wrote:
The following bug has been logged online:
Bug reference: 5317
Logged by: Marc
Email address: rasck...@gmail.com
PostgreSQL version: 8.4.2-1
Operating system: windows xp
Description: no puedo
On Thu, Feb 4, 2010 at 8:38 AM, Cristian Bittel cbit...@gmail.com wrote:
2010/2/3 Robert Haas robertmh...@gmail.com
So you're saying that if pgadmin is open when you close the terminal
services session, the SERVER crashes?
Did you somehow start the server in that same session, or is the
On Fri, Feb 5, 2010 at 9:50 PM, The Fuzzy Chef fu...@fuzzychef.org wrote:
Just had a very odd thing happen with an 8.4.2 database, and am
concerned it's an undiagnosed bug:
(1) created and dropped the same database 10-15 times in the course of
running some tests.
(2) at one point, dropdb
It's too bad you didn't capture a stack backtrace at step #3 or step
#6. If you manage to reproduce the problem, that would be a good
thing to try to get.
It never actually crashed. And, of course, this was happening right
when I needed to go home and the server needed to be up for that.
On Sat, Feb 6, 2010 at 2:36 PM, Robert Haas robertmh...@gmail.com wrote:
That's really odd. Nothing pgAdmin does should be able to crash the
PostgreSQL server, I would think. Have you got any custom code loaded
into PostgreSQL? Or non-custom, but buggy?
I'm guessing the problem only
On 2/6/10 8:20 PM, Robert Haas wrote:
On Sat, Feb 6, 2010 at 7:43 PM, The Fuzzy Chef fu...@fuzzychef.org wrote:
It's too bad you didn't capture a stack backtrace at step #3 or step
#6. If you manage to reproduce the problem, that would be a good
thing to try to get.
Well, I never got an
11 matches
Mail list logo
