[BUGS] Alternate data locations ?

2000-08-18 Thread Patrick Spinler
Hi: I'm installing postgresql-7.0.2 from ftp.postgresql.org on a clean redhat 6.2 system. I'd like to create an alternate data location, similar to that supported in pgsql 6.3, so, I do: $ export ARC_P_DAT_01="/home/httpd/data/arc_p_dat_01" $ initlocation initlocation $ARC_P_DAT_01 initlocati

Re: [BUGS] Creation of 10000's of empty table segments and more...

2000-08-18 Thread Tom Lane
"Philip Poles" <[EMAIL PROTECTED]> writes: > Basically, the backend has created a bunch of empty files of the name > ., ~32500 for one table, ~5 for another, ~44000 for > a third, and ~250 for a fourth. From reading the old thread on this, > I suspect it's being caused by the nightly vacuum w

Re: [BUGS] serial field dump bug

2000-08-18 Thread Tom Lane
Yury Don <[EMAIL PROTECTED]> writes: > After creating table with serial field if table or this field name has > an uppercase letters, sequence creating for this field doesn't double > quoted. This is already fixed for 7.1. Thanks for the report... regards, tom lane

Re: [BUGS] Segmentation fault.

2000-08-18 Thread Tom Lane
"Andrei N.Sobchuck" <[EMAIL PROTECTED]> writes: > SELECT "object"."id_object" FROM "object" WHERE "status" = 1 ) AND > ("tel" = 1 ) ) ) ) ) AND NOT(EXISTS (SELECT "po"."id_person" FROM > "person_object" "po" WHERE (("po"."id_person" = 17 ) AND ("po"."id_object" = > "object"."id_object" )

Re: [BUGS] date bug (again)

2000-08-18 Thread Tom Lane
Darcy Buskermolen <[EMAIL PROTECTED]> writes: > SELECT date_part('day', (('2000-10-1 0:00'::datetime + '1 month') + '-1 > day'))::int4 AS days_in_month; > days_in_month > -- > 30 > (1 row) This is not a bug, or at least it's not entirely clear what the behavior ought to be. The is

Re: [BUGS] INSERT/SELECT with ORDER BY

2000-08-18 Thread Stephan Szabo
Unless I'm horribly misreading the spec, this is correct. ORDER BY is used in reference to cursor definitions and direct select statements, but is not part of query expressions which is what the INSERT INTO references. ::= INSERT INTO ::=

[BUGS] default timestamp of 'now'

2000-08-18 Thread Michael Richards
I'm using postgres 7.0.2 on a FreeBSD 4.0-STABLE system. Compiled with gcc version 2.95.2 19991024 (release). When I create a table with a default timestamp of 'now' it works as expected. When I create it with the timestamp 'now'::timestamp explicitly specifying the type, it evaluates this to

[BUGS] INSERT/SELECT with ORDER BY

2000-08-18 Thread Bob Rivoir
POSTGRESQL BUG REPORT TEMPLATE Your name : Bob Rivoir Your email address : [EMAIL PROTECTED] System Configuratio