Dmitry Tkach <[EMAIL PROTECTED]> writes:
> Frankly, I don't see what is your problem with it at all :-)
Mainly, I don't like wasting cycles and code space on partial solutions
;-). There's certainly no reason you shouldn't make this patch locally
if the leak is getting in your way, but for an of
Tom Lane wrote:
>Dmitry Tkach <[EMAIL PROTECTED]> writes:
>
>>*** nodeIndexscan.c.origFri Apr 19 10:29:57 2002
>>--- nodeIndexscan.c Fri Apr 19 10:30:00 2002
>>***
>>*** 505,510
>>--- 505,514
>> */
>> ExecClearTuple(scanstate->cstate.cs_ResultTup
Dmitry Tkach <[EMAIL PROTECTED]> writes:
> *** nodeIndexscan.c.origFri Apr 19 10:29:57 2002
> --- nodeIndexscan.c Fri Apr 19 10:30:00 2002
> ***
> *** 505,510
> --- 505,514
> */
> ExecClearTuple(scanstate->cstate.cs_ResultTupleSlot);
>
Some inheritances bugss are fiked but not all
In the New version of postgresSQL (7.2.1) inheritance bug was fixed.
Now SQL99 is respect for simple inheritance behavior.
// Example :
create table people( id INT UNIQUE, name VARCHAR);
create table mother( nb_son INT) INHERITS(people);
create
Ok, this sit around for a while, and, because there was no responses, I assume, that
nothing jumps out
at you as being terribly with my logic...
Here is the patch (see the original problem description in the bottom)... It seems to
be working (at least that query,
that used to be running out of m
Alban Médici ([EMAIL PROTECTED];net) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
REFERENCES on Inherits Table
Long Description
Some inheritances bugss are fiked but not all
In the New version of postgresSQL (7.2.1) inheritance bug was fi
James Vinett <[EMAIL PROTECTED]> writes:
> ERROR: TypeCreate: type bit already defined
This is neither a bug nor a keyword conflict.
A table has a datatype of the same name associated (the composite type
corresponding to its rowtype). So, when you try to create table "bit"
that means creating
[EMAIL PROTECTED] writes:
> with psql -d nameddatabase ---> psql:error while loading shared libs : psql:
> undefined
> symbol: PQgetssl
Looks like you've got an SSL-enabled psql trying to use a
non-SSL-enabled libpq.so. I suspect you still have the 7.0 libpq
in place and the linker is finding t
I seem to be having a problem with the pg_dump command on the Linux 2.2.x
operating system. I have found that in doing a 425MB dump via TCP/IP over a
network, I receive up to 90.00 load on the dual P2 and dual P3 servers from a
start of 0.25 or so. This is a gradule increase in load peaking up t
RedHat7.1
Upgrade from pg-7.0.3.8 to pg-7.1.3 on CD 7.2
rpm upgrade of python module depndency error for module "mx" - what is this!
ignoring the python problem, installation ok, then try to use created nameddatabase
with psql -d nameddatabase ---> psql:error while loading shared libs : psql: undef
To whom it may concern:
I tried to create a new table with the following statement:
CREATE TABLE
"bit" (
provider_name varchar
);
I got the error message:
ERROR: TypeCreate: type bit already defined
According to your documentation '
11 matches
Mail list logo
