The following bug has been logged online:
Bug reference: 1044
Logged by: Denis Stepanov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Any OS lacking proper snprintf()
Description:snprintf() shipped with PostgreSQL is not thread safe
D
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes
> its own version (src/port/snprintf.c) during building. Unfortunately, this
> version of snprintf() is not reentrant (it uses global vars to keep internal
> state),
Tom Lane wrote:
> "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> > Some OSes lack proper snprintf()/vsnprintf() fuctions so PostgreSQL includes
> > its own version (src/port/snprintf.c) during building. Unfortunately, this
> > version of snprintf() is not reentrant (it uses global vars to k
Bruce Momjian <[EMAIL PROTECTED]> writes:
> What we could do is to throw a compile #error if you hit our own
> snprintf() and are compiling with threads enabled.
Good thought. If we get any complaints then we can reconsider applying
this patch, otherwise there's no need.
Hi Michael and all,
After working with Bruce last night about the
src/template/solaris file, there is a new version
of the file to be used for compiling with
--enable-thread-safety.
This version compiled without errors this time.
This version also resolved the issue with dyntest.pgc
failing in 7.
Could someone tell me if this bug is trivially reproducible or already solved before I
do a lot of needless documentation on it?
I upgraded from 7.1beta5 to 7.4.1 recently, and I noticed that many of my character
varying arrays were getting a trailing space inserted into their last value. This
I was able to do this test on a platform running 7.3.2, and the result is the same as
version 7.4.1, so if this is a bug, it is also in version 7.3.2.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Esh, Andrew
Sent: Thursday, January 08, 2004 12:53 PM
To: [
Hi PostgreSQL developers!
I'm comaintainer of the Debian package of postgresql (CC to its
maintainer) and just fixed the bug report below (see
http://bugs.debian.org/224716 for the whole thread):
- Forwarded message from simon raven <[EMAIL PROTECTED]> -
Subject: Bug#224716: postgresql-c
POSTGRESQL BUG REPORT TEMPLATE
Your name : Jason Tishler
Your email address : [EMAIL PRO
Problem occurs while restoring the database from the backup
file if i use
psql -f c:\cygwin\bin\dump_file_name -d mydatabase_name
This is not working properly...this command only creates
tables and stops...does not insert the records...
I think the “file path” causes this problem .
B
Jason Tishler wrote:
> PostgreSQL-7.4.1 fails the rules regression test with a diff such as
> the one posted to the pgsql-cygwin mailing list:
>
> http://archives.postgresql.org/pgsql-cygwin/2003-12/msg00088.php
>
> Note that I *cannot* reproduce this problem under PostgreSQL 7.4.
I think thi
The following bug has been logged online:
Bug reference: 1045
Logged by: Keith Halewood
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: HP-UX 11i
Description:hostname lookup in psql or libpg.sl does work
Details:
psql (and libpg.sl vi
"Esh, Andrew" <[EMAIL PROTECTED]> writes:
> I upgraded from 7.1beta5 to 7.4.1 recently, and I noticed that many of
> my character varying arrays were getting a trailing space inserted
> into their last value. This appears to be the result of white space
> being misplaced during the INSERT/UPDATE co
> > What I don't grok is why all the affected files were indexes, and none
> > of the heap files appeared to have junk pages
>
> Hmmm ... that is mildly interesting, but it doesn't rise to the level of
> warning bells in my head.
I played around a bit yesterday with an INSERT'ing shell script and
Martin Pitt <[EMAIL PROTECTED]> writes:
> I'm comaintainer of the Debian package of postgresql (CC to its
> maintainer) and just fixed the bug report below (see
> http://bugs.debian.org/224716 for the whole thread):
Patch applied --- many thanks!
regards, tom lane
---
Peter,
On Thu, Jan 08, 2004 at 09:47:27PM +0100, Peter Eisentraut wrote:
> Jason Tishler wrote:
> > PostgreSQL-7.4.1 fails the rules regression test with a diff such as
> > the one posted to the pgsql-cygwin mailing list:
> >
> > http://archives.postgresql.org/pgsql-cygwin/2003-12/msg00088.php
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> psql (and libpg.sl via the DBI and DBD::Pg interface) report:
> psql: could not translate host name "ysolde" to address: host nor service
> provided, or not known
Couldn't duplicate this using HP's testdrive systems (HP 11.11).
I do get a mes
The JDBC driver that ships with PostgreSQL 7.4.1 doesn't insert floats
of value NaN. As it uses Float.toString(x) to convert the value for
insertion into the database, it tries to insert NaN instead of 'NaN' and
gets the error "Attribute 'nan' not found". The same bug occurs for
doubles and w
18 matches
Mail list logo
