[BUGS] BUG #1287: Bug in www.postgresql.org php-code

2004-10-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1287
Logged by:  pre

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 8.0 Beta

Operating system:   web pages

Description:Bug in www.postgresql.org php-code

Details: 


Accessing http://archives.postgresql.org/pgsql-novice/2003-09/msg00112.php
gives the following error message:

Parse error: parse error, unexpected '<' in 
/home/web/pgsql-archives/pgsql-novice/2003-09/msg00112.php on line 87 


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


[BUGS] BUG #1288: Can't create database in a French environment

2004-10-17 Thread PostgreSQL Bugs List

The following bug has been logged online:

Bug reference:  1288
Logged by:  Jean-Philippe COURSON

Email address:  [EMAIL PROTECTED]

PostgreSQL version: 8.0 Beta

Operating system:   Slackware Linux 10.0 

Description:Can't create database in a French environment

Details: 

8.0 Beta3.

If the following environment variables are set :
LC_ALL=fr_FR
LANG=fr
initdb is unable to create the database template1.

Its output is :
...
creating template1 database in /home/pgsql/base/1 ... FATAL: XX000: failed 
to initialize lc_messages to "" 
LOCATION: InitializeGUOptions, guc.c:2360
... 




---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [BUGS] Stale entries in pg_stat_activity

2004-10-17 Thread Tom Lane
Michael Fuhr <[EMAIL PROTECTED]> writes:
 pg_stat_activity sometimes shows old connections that have already
 terminated.
>>> 
>>> Define "old"?  There's a built-in delay of up to half a second (if
>>> memory serves) in the statistics views.
>> 
>> Fourteen minutes and counting.

> Two hours and counting.  I've also reproduced the problem using
> pgbench against 8.0.0beta3 on FreeBSD 4.10-STABLE.

The other likely theory is that the stats subsystem is under
sufficiently heavy load that it drops a certain proportion of stats
messages (as it is designed to do, rather than causing foreground
activity to block).  If it were to drop a backend-termination message
then of course that connection would remain depicted in pg_stat_activity
until the stats collector figures out that the backend is gone.  Which
IIRC would normally happen when some new backend re-uses its BackendId
slot.

You could check for log messages "statistics buffer is full" as a
partial check of this theory.  This is only partial because it isn't
a direct test of whether messages are being dropped.

regards, tom lane

---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html


Re: [BUGS] BUG #1288: Can't create database in a French environment

2004-10-17 Thread Tom Lane
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:
> If the following environment variables are set :
> LC_ALL=fr_FR
> LANG=fr
> initdb is unable to create the database template1.

> Its output is :
> ...
> creating template1 database in /home/pgsql/base/1 ... FATAL: XX000: failed 
> to initialize lc_messages to "" 
> LOCATION: InitializeGUOptions, guc.c:2360

Take it up with Slackware: evidently they have broken support for that
locale.

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


Re: [BUGS] BUG #1236: still in use tablespaces can be removed

2004-10-17 Thread Bruce Momjian

I can confirm this is fixed in current CVS:

test=> CREATE TABLESPACE tsp LOCATION  '/bjm/tmp';
CREATE TABLESPACE
test=> CREATE SCHEMA s TABLESPACE tsp;
CREATE SCHEMA
test=> DROP TABLESPACE tsp;
DROP TABLESPACE
test=> CREATE TABLE s.t(id SERIAL PRIMARY KEY);
NOTICE:  CREATE TABLE will create implicit sequence "t_id_seq" for
serial column "t.id"
ERROR:  tablespace with OID 17231 does not exist
DETAIL:  The default tablespace for schema "s" has been dropped.


---

PostgreSQL Bugs List wrote:
> 
> The following bug has been logged online:
> 
> Bug reference:  1236
> Logged by:  Fabien
> 
> Email address:  [EMAIL PROTECTED]
> 
> PostgreSQL version: 8.0 Beta
> 
> Operating system:   Linux debian
> 
> Description:still in use tablespaces can be removed
> 
> Details: 
> 
> Sorry if this bug was already reported.
> I could not search the list as http://archives.postgresql.org/pgsql-bugs/
> looks blank right now...
> 
> One can remove a tablespace although it is being
> used, putting the database in a slightly incoherent
> state. It was so in yesterday (27/08/2004) cvs head:
> 
> sh> mkdir /tmp/postgres
> pg> CREATE TABLESPACE tsp LOCATION '/tmp/postgres';
>   -- ok
> pg> CREATE SCHEMA s TABLESPACE tsp;
>   -- ok
> pg> DROP TABLESPACE tsp;
>   -- ok...
> pg> CREATE TABLE s.t(id SERIAL PRIMARY KEY); 
>   -- ERROR... cannot create directory
> 
> The bug is simply that DROP TABLESPACE looks whether
> the directory is empty, but it happens that the namespace's tablespace uses 
> do not create anything in the directory... 
> 
> I now that I can alter the tablespace entry manually
> in pg_namespace to correct this, but it looks like a bug to me anyway: the 
> database should not be so easy 
> to put in a in coherent state.
> 
> Suggested fix: create some empty file in the directory
> if it is used by a namespace. don't forget to move
> the file around when altering the namespace (well, once
> it will be implemented).
> 
> It does not seems practical to check for namespace's uses of a tablespace as 
> one belong to a cluster and the other to the database. 
> 
> 
> ---(end of broadcast)---
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> 

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

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


[BUGS] Mac OS X make check errors...

2004-10-17 Thread Theodore Petrosky
Hi all,

I just tried the newest beta (3) and for the first
time I am getting multiple errors in 'make check'.

this is my configure line...

./configure --with-rendezvous --enable-thread-safety
--disable-shared

 I inserted the --disable-shared from a recomendation
to not create the shared libraries as i use libpq.a
exclusively.

I will see if removing it helps.

Is there something I should be aware of?

Ted


parallel group (7 tests):  create_aggregate
create_operator triggers vacuum constraints inherit
create_misc
 constraints  ... ok
 triggers ... FAILED
 create_misc  ... ok
 create_aggregate ... ok
 create_operator  ... ok
 inherit  ... ok
 vacuum   ... ok
parallel group (2 tests):  create_view create_index
 create_index ... ok
 create_view  ... ok
test sanity_check ... ok
test errors   ... ok
test select   ... ok
parallel group (18 tests):  select_distinct_on update
select_having select_distinct select_into union case
namespace random select_implicit aggregates hash_index
arrays transactions portals btree_index join subselect
 select_into  ... ok
 select_distinct  ... ok
 select_distinct_on   ... ok
 select_implicit  ... ok
 select_having... ok
 subselect... ok
 union... ok
 case ... ok
 join ... ok
 aggregates   ... ok
 transactions ... FAILED
 random   ... ok
 portals  ... ok
 arrays   ... ok
 btree_index  ... ok
 hash_index   ... ok
 update   ... ok
 namespace... ok
test privileges   ... ok
test misc ... ok
parallel group (5 tests):  portals_p2 select_views
cluster rules foreign_key
 select_views ... ok
 portals_p2   ... ok
 rules... ok
 foreign_key  ... ok
 cluster  ... ok
parallel group (14 tests):  limit copy2 sequence
truncate temp polymorphism conversion prepare domain
rowtypes rangefuncs plpgsql without_oid alter_table
 limit... ok
 plpgsql  ... failed (ignored)
 copy2... FAILED
 temp ... ok
 domain   ... ok
 rangefuncs   ... FAILED
 prepare  ... ok
 without_oid  ... ok
 conversion   ... FAILED
 truncate ... ok
 alter_table  ... ok
 sequence ... ok
 polymorphism ... ok
 rowtypes ... ok
test stats... FAILED
test tablespace   ... ok
== shutting down postmaster  
==
postmaster stopped


 7 of 96 tests failed, 1 of these failures ignored. 




___
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

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


Re: [BUGS] Mac OS X make check errors...

2004-10-17 Thread Neil Conway
On Mon, 2004-10-18 at 12:55, Theodore Petrosky wrote:
> I just tried the newest beta (3) and for the first
> time I am getting multiple errors in 'make check'.

Can you post the regression.diffs file produced by "make check" (should
be in src/test/regress under the directory in which you build
PostgreSQL).

-Neil



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]