Michael Handler ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
MACADDR type & 00:00:00:00:00:00
Long Description
postgresql version 7.1.3, compiled with gcc 2.95.2 on solaris 2.6, running on solaris
2.8.
provisioning=> \d en
Sndor, Vig ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
ODBC problem at migrating 7.0 to 7.1
Long Description
I wrote an application (in Borland CBuilder) that uses ODBC to access
a DB. First I used Psql 6.5, then 7.0 withou
> MACADDR type & 00:00:00:00:00:00
> postgresql version 7.1.3, compiled with gcc 2.95.2 on solaris 2.6, running on
>solaris 2.8.
...
> provisioning=> select macaddr '00:00:00:00:00:00';
> it's not null, so shouldn't it be retrieving as '00:00:00:00:00:00'?
> not that i ever expect to encounter th
[EMAIL PROTECTED] writes:
> it's not null, so shouldn't it be retrieving as '00:00:00:00:00:00'?
Yeah, due to some brain-fade on the part of the original implementor,
the code went out of its way to special-case 00:00:00:00:00:00 as
being represented by an empty string. This was agreed to be bro
postgres@abigail ~/data $ createdb test1
Password:
CREATE DATABASE
postgres@abigail ~/data $ createlang --dbname=test1 --pglib=/usr/lib/pgsql
'plpgsql'
Password: Password: Password:
Password:
postgres@abigail ~/data $ createlang --list --dbname=test1
Password:
Procedural languages
Name
Severity: Major
Short description: Problem with ODBC Driver Version 7.1.9, DB Version 7.1.3
Long description:
created table umsatz:
fakt32=# \d umsatz
Table "umsatz"
Attribute | Type | Modifier
+---
Hi, I'm running 7.1.3 on a redhat linux system, using the rpm packages from
the postgresql site:
[nova@naomi scripts]$ rpm -qa|grep postgresql
postgresql-libs-7.1.3-0.onms.5
postgresql-server-7.1.3-0.onms.5
postgresql-python-7.1.3-0.onms.5
postgresql-7.1.3-0.onms.5
postgresql-contrib-7.1.3-0.onms
well, i will be a little verbose, but i am afraid this could be a big bug
in postgresql, so...
i've made a script in python that, by psycopg module, put freecddb archive
in a relational db. so, it does a few select and a lot of insert for each
file of freecddb (something like 500.000 files).
now,
Hello,
I am a postgres novice. I was trying to install pltclu for running some tcl
function to enable mailing from postgres. But I am not able to find the
required shared object file (.so extension) for installing that language. I
am able to install the language pltcl using the file pltcl.so. How
postgresql version 7.1.3, compiled with gcc 2.95.2 on solaris 2.6, running
on solaris 2.8.
provisioning=> \d enduser
Table "enduser"
Attribute| Type| Modifier
-+---+
account
Hi!
My C program executes a pretty complex query (of length about 600 chars,
with subqueries, etc.).
When I run it (on Linux), it crashes with "Segmentation fault (core
dumped)".
I'm sure that the program crashes on this specific PQexec command.
Is there a length limit for queries in PQexec, or
On Fri, Jan 04, 2002 at 01:52:32PM -0500, Bruce Momjian wrote:
> Looking at this I also found an ecpg TODO list in the docs:
>
> http://candle.pha.pa.us/main/writings/pgsql/sgml/ecpg-develop.html
>
> Seems that TODO section should be removed. Some items are done, others
> are on the main
On Fri, Jan 04, 2002 at 04:02:14PM +, Lee Kindness wrote:
> Michael, hope you've had a good Christmas & all the best for the New
> Year...
Sure. Thanks.
> When you run 'ecpg --help' you get the following:
>
> -t turn on autocommit of transactions
>
> amongst the other options...
Please, ignore my question. The problem was that I did PQclear(res) before
calling to PQgetvalue(res,...)
Anyway, it should not crush (IMHO).
Alex
"Alex Glikson" <[EMAIL PROTECTED]> wrote in message
a1jjj5$tas$[EMAIL PROTECTED]">news:a1jjj5$tas$[EMAIL PROTECTED]...
> Hi!
>
> My C program execute
I'm getting "Bad integer 4020239173" error. From what I found on the
Web it seems to be a Postgres bug, not specific to any programming
language. I've found PHP and Java guys complaining about it (I'm
using JDBC). However, I failed to find resolution of this problem.
Can you suggest som
I have noticed that some of the command line tools do not work nicely
when the local auth is not set to trust, but trust is dangerous. Have
you tried creating the language from psql rather than from the command line?
[EMAIL PROTECTED] wrote:
>postgres@abigail ~/data $ createdb test1
>Password
andrea gelmini <[EMAIL PROTECTED]> writes:
> vacuumdb -a -v -f -z
> NOTICE: Analyzing author
> FATAL 2: open of /home/postgres/db/pg_clog/ failed: No such file or directo
> ry
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> be
my database create -E UNICODE
can't run
timestamp(date '2000-12-25')
error message>> parse error at or near "date"
lpad('hi',4,'??') >> not return '??hi'
rpad('hi',4,'x') >> return error string
--
---(end of broadcast)---
TIP 5: Have yo
Dmitry Macsema <[EMAIL PROTECTED]> writes:
> I'm getting "Bad integer 4020239173" error. From what I found on the
> Web it seems to be a Postgres bug, not specific to any programming
> language.
First I've heard of it. You're going to have to provide a lot more
information if you want us t
andrea gelmini <[EMAIL PROTECTED]> writes:
> On ven, gen 11, 2002 at 01:56:12 -0500, Tom Lane wrote:
>> Yup, it looks like a bug to me. Apparently a CLOG segment has been
>> recycled too soon. We just found a bug of that ilk in sequence
>> processing, but VACUUM doesn't touch sequences, so appar
>
> Sndor, Vig ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> ODBC problem at migrating 7.0 to 7.1
>
> Long Description
> I wrote an application (in Borland CBuilder) that uses ODBC to access
> a DB. First I used Psql
21 matches
Mail list logo
