Peter Eisentraut <[EMAIL PROTECTED]> writes:
> The platfrom which we are using is Digital V4.0-D (alphaev56-dec-osf4.0d).
> I copied the whole configuration report for you, maybe it helps.
> I'm acctually suspecting our GCC version (v2.7.2.3), maybe it's too old and
> not familiar with "-mieee" op
Christian Breimann <[EMAIL PROTECTED]> writes:
> select distinct S.customer_name
> from depositor as S
> where not exists(
> (select branch_name
> from branch
> where branch_city='Brooklyn')
> except
> (select R.branch_name
>
Known issue, see FAQ item 4.23. Short form, use exists rather
than in.
On Tue, 8 May 2001, [KOI8-R] þÅÒÅÐÁÎÏ× ìÅÏÎÉÄ wrote:
> Leonid ([EMAIL PROTECTED]) reports a bug with a severity of 2(?)
>
> Short Description
> Terrible perfomance during nested "... where x in (select ...)" operator
>
>
Fariba Noorbakhsh <[EMAIL PROTECTED]> writes:
> The platfrom which we are using is Digital V4.0-D (alphaev56-dec-osf4.0d).
> I copied the whole configuration report for you, maybe it helps.
> I'm acctually suspecting our GCC version (v2.7.2.3), maybe it's too old and
> not familiar with "-mieee" o
"Jerry Davis" <[EMAIL PROTECTED]> writes:
> CREATE SEQUENCE login_primary_key_seq start 1 increment 1 maxvalue
> 2147483647 minvalue 1 cache 1 ;
> SELECT nextval ('login_primary_key_seq');
> Is there something missing from the original database that got
> dumped, or something I have to manually
Fariba Noorbakhsh <[EMAIL PROTECTED]> writes:
> gcc -Wall -Wmissing-prototypes -Wmissing-declarations -mieee
> -I../../../../src/include -c acl.c -o acl.o
> cc1: Invalid option `ieee'
> gmake[4]: *** [acl.o] Error 1
Hm. It looks like configure is choosing the wrong compiler options for
your p
Vinicio Llumiquinga <[EMAIL PROTECTED]> writes:
> fmgr_info: function 18816: cache lookup failed
> This happend when I write any function.
I suspect you dropped the plpgsql call handler function.
If so, the only convenient recovery method AFAIK is to drop the
plpgsql language entry and all your
[EMAIL PROTECTED] writes:
> I'm unable to build on Irix (6.5.9) using the MipsPro compiler (Vs 7.3). The output
>is this:
> cc-1092 cc: ERROR File = ../../../../src/include/utils/nabstime.h, Line = 157
> Identifier-list parameters can only be used in a function definition.
> extern Datum ti
How do I stop this information from coming to me?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 9:35 AM
To: Christian Breimann
Cc: [EMAIL PROTECTED]
Subject: Re: [BUGS] exists <==> not exists ???
Christian Breimann <[EMAIL PROTECTED]> writes:
>
Vince Vielhaber <[EMAIL PROTECTED]> writes:
> If this:
> alter table foobar add column address varchar(50) default 'none';
> is the incorrect syntax, why does it not fail or at least give a
> warning?
Because it's incompletely implemented: the parser takes the full syntax
but the ALTER TABLE rout
"Jerome O'Neil" <[EMAIL PROTECTED]> writes:
> Which makes me wonder: What is the point, if not to
> restrict updatability?
Postgres' SELECT FOR UPDATE marks rows for update, not columns.
Thus nominating columns in it would make no sense.
It was probably an unfortunate decision to use "FOR UPDAT
Christian Breimann <[EMAIL PROTECTED]> writes:
> When executing a SQL-Query with a "where not exists (...)" Statement,
> the result is wrong. It's the same result as I execute "where exists
> (...)" This mustn't be true.
This is a completely unhelpful bug report. We need sufficient details
to le
When Postgres is configured and decides to use libncurses and
libreadline, the backend gets linked against those two libs, too, even
though it really doesn't use them. This is just extra wasted size and
(if they're shared libs) dependencies you don't need.
I made this ultra-cheesy change to src/
Hi,
i think i found a bug in the pgsql interpreter. Platform is
Linux-2.4.0 on Intel, Postgres-Version is 7.1.1 .
The Problem:
I want to use a table name in a select statement within a function,
where the table name comes in as argument. It only works, if at all,
inside an execute statement. Wh
I have a problem
I have a function in plpgsql:
create function add_one (integer) returns integer as '
begin
return $1+1;
end;
' language 'plpgsql';
When I create in psql monitor this function the message is CREATED
Then I write:
select add_one(1);
and always say:
fmgr_info: function 18816:
Hi!
I am facing two problems in porting from oracle to Postgres SQL.
1> There is a code in Oracle like
Type Tstate is table of number(9)
index by binary_integer;
.
To define a runtime table, basically it works like a array, How can it
be possible in Postgres SQL,
I have tried crea
Here is a short example where this touchy bug
occurs :
create database mydb;
\c mydb
create table temp ( name varchar(12));
insert into temp values ('eric');
insert into temp values ('daniel');
insert into temp values ('ernst');
insert into temp values ('chantal');
having the four names abo
Hello,
I tried to install PstgreSQL 7.1.1, and I got these error log:
gmake[3]: Leaving directory
`/users/noorbakh/postgreSQL/postgresql-7.1.1/src/backend/tcop'
gmake -C utils all
gmake[3]: Entering directory
`/users/noorbakh/postgreSQL/postgresql-7.1.1/src/backend/utils'
gmake -C adt SUBSYS.o
g
> "PG" == Palle Girgensohn <[EMAIL PROTECTED]> writes:
PG> You should really use the port. it has a working startup
PG> script, and it creates a pgsql/.profile for you. Using su -m is
PG> more error prone IMHO. It will export locales and such, that
PG> you really don't want to export to postm
On 8 May 2001, Nabil Sayegh wrote:
> On 05 May 2001 12:23:37 -0400, [EMAIL PROTECTED] wrote:
> > Vince Vielhaber ([EMAIL PROTECTED]) reports a bug with a severity of 3
> > The lower the number the more severe it is.
> >
> > Short Description
> > Alter table add column ignores default
> >
> > Long
On 8 May 2001, Nabil Sayegh wrote:
> On 08 May 2001 10:31:17 -0400, Vince Vielhaber wrote:
> > > http://hermes.swu.bg/postgres/postgres/sql-altertable.htm
> > > The correct syntax is:
> > > ALTER TABLE foobar add column address varchar(50);
> > > ALTER TABLE foobar alter column address set defaul
Hello,
I think, that I've found one bug in PostgreSQL 7.1 on
sparc-sun-Solaris2.7, compilied by GCC 2.7.2.3:
When executing a SQL-Query with a "where not exists (...)" Statement,
the result is wrong. It's the same result as I execute "where exists
(...)" This mustn't be true.
Is this a known b
Hi
I'm using postgres 7.1.1 version tar format. I've compiled and installed
with the default option
1) ./configure
2) make
3) make install
4) create a data dir with postgres user permission
in /usr/local/pgsql/data
5) initdb -D /usr/local/pgsql/data
- NO ERROR encounter.
6) start postmas
In short, when I try to restore a database from a pg_dump
generated SQL script, then try to insert additional records
into the restored datbase, it gives me a duplicate key error.
I am using the following version of the PostgreSQL database:
PostgreSQL 7.0.3 on i686-pc-linux-gnu, compiled by gcc
Leonid ([EMAIL PROTECTED]) reports a bug with a severity of 2(?)
Short Description
Terrible perfomance during nested "... where x in (select ...)" operator
Long Description
PostgreSQL 7.1, FreeBSD 4.2-STABLE
Analyzing the reasons for terrible perfomance of my query I've found
a very strange thi
* Tom Lane <[EMAIL PROTECTED]>:
| Evidently you're using the newly-released readline 4.2.
|
| Update to PG 7.1.1, or downgrade to readline 4.1.
Thank you Tom, 7.1.1 works fine with readline 4.2.
---(end of broadcast)---
TIP 6: Have you searched o
Erik Hofman ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Irix build failes (PSQL 7.1.1)
Long Description
I'm unable to build on Irix (6.5.9) using the MipsPro compiler (Vs 7.3). The output is
this:
cc-1092 cc: ERROR File =
27 matches
Mail list logo
