[EMAIL PROTECTED] writes:
> tab-complete.o: In function `psql_completion':
> tab-complete.o(.text+0x53): undefined reference to `rl_completion_append_character'
> tab-complete.o(.text+0x1496): undefined reference to `rl_completion_append_character'
What Postgres version are you using? There's be
Branson Matheson ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
FreeBSD 4.2 readlib issue
Long Description
Compiling under freebsd gives this problem:
gcc -I../../include -I../../backend -O2 -m486 -pipe -Wall -Wmissing-proto
Szima Gabor ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
foreign key check makes a big LOCK
Long Description
in: src/backend/utils/adt/ri_triggers.c
RI_FKey_check(), RI_FKey_noaction_upd(), RI_FKey_noaction_del(), etc..
che
"Joel Burton" <[EMAIL PROTECTED]> writes:
> Just to be clear (as much for other as for me): this should fix the
> syntax as my (more recent) bug report submitted? That is, one non-
> conditional rule that tries to handle both inserting and updating
> together, as opposed to 2 different condition
> It turns out that all of these failures come from the same place,
> which is that I had broken the handling of INSERT ... SELECT actions
> inside rules.
>
> I have committed a patch that appears to fix the problem.
> I think that Marc has already tagged beta1, however, so the patch will
> not b
Nabil Sayegh <[EMAIL PROTECTED]> writes:
> There seems to be a bug in postgresql concerning UNION.
Cross-datatype UNION doesn't work very well at all in existing releases.
I recommend making sure the constants in the second SELECT exactly match
the types of the variables in the first select, usin
"Joel Burton" <[EMAIL PROTECTED]> writes:
> Tom Lane pointed out that, given the current handling of
> conditional rules, this should be one rule, with two
> actions.
> For, this either fails to work, or in some circumstances,
> or in some circumstances, crashes the backend.
It turns out that a
Hi,
There seems to be a bug in postgresql concerning UNION.
I use 7.0.3 (BLCKSIZE=32)
I have the following tables:
Table "best_ez"
Attribute | Type |
Modifier
+--+--
Tim Dunnington ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
createlang requires entering password 4 times
Long Description
When you run createlang, and you are using password authentication, you have to type
in the password
[EMAIL PROTECTED] writes:
> I have included all code needed to prove the bug,
No, you haven't: where are the table declarations?
But I'll take a guess anyway: you declared "distance" as int2, didn't
you? AVG(int2) currently uses an int2 accumulator, and you're suffering
overflow. Try "AVG(dist
[EMAIL PROTECTED] wrote:
>
> Gavin Evans ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> Aggregate Function (AVG) not calculated correctly
>
> Long Description
> Using the following code:
> SELECT airline_code, AVG(dis
Gavin Evans ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Aggregate Function (AVG) not calculated correctly
Long Description
Using the following code:
SELECT airline_code, AVG(distance) FROM flights GROUP BY airline_code;
Th
Laurent Larquere ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
perl5 interface Pg.xs compile
Long Description
Not really a bug, but ...
PG version 7.0.2 and 7.0.3
On Solaris 8, perl 5.6.0 :
In the file src/interfaces/perl5/Pg
13 matches
Mail list logo
