Re: [BUGS] postgresql installation on centOS not working

2006-12-13 Thread Heikki Linnakangas

Danish Siddiqui wrote:

Heikki Linnakangas wrote:

Danish Siddiqui wrote:

Im not able to install postgresql-8.1.2 on CentOS 4.1


What's the error you're getting?


When I do
#./configure

it configures and shows statements that its creating the make file and 
checking all the dependencies..but then when I do

#make
it again starts checking for all the dependencies and this keeps on 
repeating...


Please keep the mailing list cc'd!

I'm no Makefile guru, but that sounds like an issue with modification 
timestamps on the files. I'd suggest checking the timestamps on 
config.status. I can reproduce that behavior if I run "touch -d 
2007-01-01 configure". If that's your problem, "touch configure" should 
help.


--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match


[BUGS] 8.1.2 -32768::smallint

2006-12-13 Thread Jean-Gérard Pailloncy
Hi,

On PostgreSQL 8.1.2
select -32768::smallint
throws the error
ERROR:  smallint out of range

select -32767::smallint
is OK.

The documentation states that -32768 is OK.
http://www.postgresql.org/docs/8.1/interactive/datatype.html#DATATYPE-NUMERIC

Cordialement,
Jean-Gérard Pailloncy


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [BUGS] 8.1.2 -32768::smallint

2006-12-13 Thread Michael Fuhr
On Wed, Dec 13, 2006 at 03:03:43PM -, Jean-Gérard Pailloncy wrote:
> On PostgreSQL 8.1.2
> select -32768::smallint
> throws the error
> ERROR:  smallint out of range

I think the cast is binding tighter than the unary minus, so the
above is equivalent to

select -(32768::smallint)

which is why you're getting "smallint out of range."  This should work:

select (-32768)::smallint

-- 
Michael Fuhr

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [BUGS] 8.1.2 -32768::smallint

2006-12-13 Thread Michael Fuhr
On Wed, Dec 13, 2006 at 08:34:38AM -0700, Michael Fuhr wrote:
> On Wed, Dec 13, 2006 at 03:03:43PM -, Jean-Gérard Pailloncy wrote:
> > On PostgreSQL 8.1.2
> > select -32768::smallint
> > throws the error
> > ERROR:  smallint out of range
> 
> I think the cast is binding tighter than the unary minus,

Indeed it is; see the Operator Precedence table:

http://www.postgresql.org/docs/8.1/interactive/sql-syntax.html#SQL-PRECEDENCE

-- 
Michael Fuhr

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [BUGS] 8.1.2 -32768::smallint

2006-12-13 Thread Jean-Gérard Pailloncy
> select -(32768::smallint)
>
> which is why you're getting "smallint out of range."  This should work:
>
> select (-32768)::smallint
Exact. Thank you for the answer.
But really conter-intuitive.

Cordialement,
Jean-Gérard Pailloncy


---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [BUGS] postgresql installation on centOS not working

2006-12-13 Thread Tom Lane
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Danish Siddiqui wrote:
>> it configures and shows statements that its creating the make file and 
>> checking all the dependencies..but then when I do
>> #make
>> it again starts checking for all the dependencies and this keeps on 
>> repeating...

> I'm no Makefile guru, but that sounds like an issue with modification 
> timestamps on the files. I'd suggest checking the timestamps on 
> config.status.

No, just fix your system clock setting.  This is the standard behavior
seen when the source files have timestamps "in the future" according
to the system clock --- make keeps trying to generate derived files
that are newer, and yet they still seem to be out of date compared
to the sources ...

regards, tom lane

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [BUGS] ERROR: failed to build any 4-way joins

2006-12-13 Thread Teodor Sigaev

went up in smoke, and I ended up just having have_relevant_joinclause()


Thank you a lot, I was near around it :)

--
Teodor Sigaev   E-mail: [EMAIL PROTECTED]
   WWW: http://www.sigaev.ru/

---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

   http://www.postgresql.org/about/donate


[BUGS] the bug report form doesn't accepts the email address

2006-12-13 Thread Gergely CZUCZY
hello

the bug reporting form on the website does not accept
any valid email address i fill it with.
http://wwwmaster.postgresql.org/system/handleform.php

i had tried [EMAIL PROTECTED]'' and [EMAIL PROTECTED]''.
both are valid, working email addresses.

Bye,

Gergely Czuczy
mailto: [EMAIL PROTECTED]

-- 
Weenies test. Geniuses solve problems that arise.


pgpdhx3cb9yaN.pgp
Description: PGP signature


[BUGS] fkey+inheritance issue

2006-12-13 Thread Gergely CZUCZY
Hello

i had written a bug report on the web-based for, but
it hadn't accepted my email address, so i'm trying to
report this here.

PostgreSQL version:
PostgreSQL 8.2.0 on i386-portbld-freebsd6.1, compiled by GCC cc (GCC) 3.4.4 
[FreeBSD] 20050518

OS: FreeBSD 6.1-RELEASE-p10

Short descr:
fkey cannot reference to an inherited table's child's tuple through the ancestor

Details:
hen given an inherited table structure and one other table's FKEY uses the 
supertable's inherited PKEY as a reference, it gets an error when it comes to 
child table's tuples.

whereas in sql-createtable.html it's said that then children's data can be 
accessed through the parent table(s).

the following code demonstrates the issue well:


CREATE TABLE "ancestor" (
"id"integer NOT NULL,
"name"  varchar(32) NOT NULL,
PRIMARY KEY ("id")
);

CREATE TABLE "child" (
"attr1" integer NOT NULL
) INHERITS ("ancestor");

CREATE TABLE "reference" (
"id"integer NOT NULL,
"ancid" integer NOT NULL,
PRIMARY KEY ("id"),
FOREIGN KEY ("ancid")   REFERENCES  "ancestor"("id")
);

INSERT INTO "ancestor" (id,name) VALUES (1,'ancfoo');
INSERT INTO "child" (id,name,attr1) VALUES (2,'childfoo', 2);
INSERT INTO "reference" (id,ancid) VALUES (1,1);
-- till here it's OK
INSERT INTO "reference" (id,ancid) VALUES (2,2);
-- here:
-- ERROR:  insert or update on table "reference" violates foreign key 
constraint "reference_ancid_fkey"
-- DETAIL:  Key (ancid)=(2) is not present in table "ancestor".


Bye,

Gergely Czuczy
mailto: [EMAIL PROTECTED]

-- 
Weenies test. Geniuses solve problems that arise.


pgp5jMHmJXV5T.pgp
Description: PGP signature