At 16:17 12/04/01 -0400, [EMAIL PROTECTED] wrote:
>Patricia Holben ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>table data not being restored after pg_dump
...
>but the table f_star can not be reloaded. The error messag
Giuseppe Sacco ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
bug in 7.0.3 related to triggers and field rename
Long Description
Hi,
I probably found a bug in PostgreSQL 7.0.3 running on Debian GNU/Linux potato. Kernel
2.2.19
"Kyle F. Downey" <[EMAIL PROTECTED]> writes:
> In 7.1rc2, this same DDL results in this error:
> ERROR: UNIQUE constraint matching given keys for referenced table
> "incidents" not found
7.1 enforces the requirement that the referenced column be marked UNIQUE
(or PRIMARY KEY, which implies UNI
"Rick Touchette" <[EMAIL PROTECTED]> writes:
> In order to get the runtest regression test to work I had to change line 100
> in regress.sh
> from:
> createlang $HOSTLOC plpgsql regression
> to:
> createlang -L /home/n33rta/pgsql/lib $HOSTLOC plpgsql regression
> (I had to speci
Nick Wellnhofer <[EMAIL PROTECTED]> writes:
> further investigatoin showed that a simple "SELECT * FROM url" query
> resulted in
> Backend message type 0x44 arrived while idle
> pqReadData() -- backend closed the channel unexpectedly.
Are you sure this is a backend crash? (Real proof would be a
Holger Klawitter <[EMAIL PROTECTED]> writes:
> Upgrading from 7.0.3 to 7.1(rc4) went very smooth - but a small
> issue came up:
> The following statement does not work any more:
> update l set i=2 from longname l where l.i=1;
I'd say it's a fluke that that ever was accepted. Given the obv
Ken-ichi Yamasaki <[EMAIL PROTECTED]> writes:
> I build PostgreSQL 7.0.3 with jumbo-20010318.patch.gz on Vine Linux2.1.5.
> Following result are incorrect. Am I under an illusion?
> test=# select '3424082'::numeric % '3471'::numeric;
> ?column?
> --
>-46918
> (1 row)
This
Thus spake Kevin Cole
> I'm cc'ing the pgsql-bugs address, since I'm starting to think it's
> their problem.
>
> It appears that the folks at www.postgresql.org don't know about pgdb.py
> either. Or, rather, not consistently. Apparently, the 7.0.3-2 source
> tarball doesn't equal the 7.0.3-2 sou
Hi
I've tried to put together a schema, in 7.1 RC 3, when the following
"error" occured:
After dragging a table, and selecting another one, both tables were
dragged. The same happened when I was linking tables, and I couldn't
do anything to separate them...
Lehel
---(e
Hello all,
I'm cc'ing the pgsql-bugs address, since I'm starting to think it's
their problem.
It appears that the folks at www.postgresql.org don't know about pgdb.py
either. Or, rather, not consistently. Apparently, the 7.0.3-2 source
tarball doesn't equal the 7.0.3-2 source RPM.
I just downl
Hi,
I'm trying to compile Postgres under HP-UX after having installed GCC 2.95 and
GMake.
After deleting config.cache I run succesfully configure.
When I start to compile I get the following message and the compilation stops:
root@ipa9h06:/mnt06/users/upsdev/postgres/src >gmake
gmake -C utils a
Antonio Sindona <[EMAIL PROTECTED]> writes:
> I'm trying to compile Postgres under HP-UX after having installed GCC 2.95 and
> GMake.
It looks like configure has decided to try to use cc, not gcc, which
will not work too well unless you have HP's full ANSI C compiler.
The K&R C they give you for
12 matches
Mail list logo
