[EMAIL PROTECTED] writes:
> [several occurrences of]
> ! ERROR: datumGetSize: Invalid typLen 0
This seems like a clear bug --- but given the lack of similar reports
from other users of Linuxen and Alphas, I'm not entirely convinced it's
Postgres' bug. Possibly a compiler or library bug on your p
ttn ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
7.3.1 on linux-alpha: 3 "make check" tests fail
Long Description
platform (uname -a):
Linux alphasql 2.4.18-rc2 #2 Wed Feb 20 02:49:42 EST 2002 alpha unknown
gcc --version:
2.
[EMAIL PROTECTED] writes:
> I added the arguments to configure
> --with-tcl --with-tclConfig=/usr/lib, --with-tkConfig=/usr/lib
You spelled those switches wrong (should be "--with-tclconfig",
"--with-tkconfig") but they oughtn't be necessary anyway if you
have tcl installed into the standard syst
On Thursday 26 December 2002 06:09 pm, Tom Lane wrote:
> Is it likely that someone else was doing the same thing in another
> session?
no ANALYZE in parallel but another client constantly running transactions
(over 6 tables with approx. 20 - 100 updates/inserts per transaction).
The postgres clien
[EMAIL PROTECTED] writes:
> [linux-xfs-host]$ pg_dump db -Fc -f dump
> Segmentation fault (core dumped)
Can you provide a stack trace from the core file? It would also be
useful to see the last few SQL commands issued by pg_dump --- easiest
way to do this is enable query logging via
expor
Lamar Owen <[EMAIL PROTECTED]> writes:
> Tom, Bruce: who has the python interface these days?
D'Arcy still is the lead guy on it, I think. Looking at the CVS logs,
it seems this problem was fixed in CVS HEAD but not back-patched into
the 7.3 branch:
2002-12-04 07:23 darcy
* src/interfa
Sorry. Interesting the workaround doesn't work in 7.2.X. Hopefully we
will get this worked out in 7.4.
---
JMM Moi-Meme Maitre du Monde wrote:
> Wrong ! The workaround works in 7.3 but is not backward compatible
> with pri
[EMAIL PROTECTED] writes:
> bitfromint4 not present in 7.3.1
This is not a bug, but an intentional change. It's called "bit" now,
as it should have been all along --- the original author was apparently
unaware of the naming conventions Postgres has for type-coercion
functions.
Harald Krake <[EMAIL PROTECTED]> writes:
> while running a "vacuumdb -z" I got the following error message:
> ERROR: simple_heap_update: tuple concurrently updated
> vacuumdb: vacuum jartifice failed
Is it likely that someone else was doing the same thing in another
session? This failure is kno
[EMAIL PROTECTED] writes:
> postgresql=# CREATE USER mpech777;
> CREATE USER
> postgresql=# alter USER mpech777 password '';
> server closed the connection unexpectedly
Hm, it works fine here. You'll need to give more details about
platform, configuration options, any nondefault settings in
p
On Thursday 26 December 2002 07:15, Gaetano Mendola wrote:
> I already post the fact that the file pgdb.py distribuited with
> Postgres 7.3 is wrong but was not already fixed in 7.3.1
> why was not yet corrected ?
It is not an RPM specific problem, but your subject implies that it is.
Tom,
Kenji Sugita <[EMAIL PROTECTED]> writes:
> Functions bittoint4 and bitfromint4 are renamed to int4 and bit respectively.
> Int4 works well, but bit conflicts with type bit.
Spell it with quotes, or use cast syntax.
regression=# select "bit"(44);
bit
Andrew Goldsmith ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
bitfromint4 not present in 7.3.1
Long Description
I have installed a copy of PostgreSQL 7.3.1 from src on my Debian/Linux system. The
bitfromint4 function is no
Wrong ! The workaround works in 7.3 but is not backward compatible
with prior 7.x.y version.
I began reverting to 7.2.3 :( Anyway, I will survive ;)
On Thu, Dec 26, 2002 at 09:02:08AM +0100, JMM Moi-Meme Maitre du Monde wrote:
> Yes, it works. Thanks.
>
> I will just have to alter some 50 script
I already post the fact that the file pgdb.py distribuited with
Postgres 7.3 is wrong but was not already fixed in 7.3.1
The class pgdbTypeCache is not working with the version 7.3.1
the method getdescr try to do the following select:
"SELECT typname, typprtlen, typlen FROM pg_type"
and th
Yes, it works. Thanks.
I will just have to alter some 50 scripts, but that's better than
having to revert my DBs (~18 GB) to 7.2.3 while waiting for 7.4.
On Wed, Dec 25, 2002 at 10:58:41PM -0500, Bruce Momjian wrote:
>
> This is a known problem with 7.3.X. It doesn't create an oid column as
> p
16 matches
Mail list logo
