Re: [pgadmin-hackers] Handling the pg_global of tablespace.

2007-10-12 Thread Dave Page
Hiroshi Saito wrote:
 From: Dave Page [EMAIL PROTECTED]
 
 It should still work for superusers though shouldn't it?

 
 Eh?, Is it ACL bug of PostgreSQL ver 8.3b1?
 
 As for superuser,
 2007-10-11 13:53:23 ERROR  : ERROR:  permission denied for tablespace
 pg_global

Yes, I specifically asked Tom about the superuser case and he responded:
 http://archives.postgresql.org/pgsql-hackers/2007-08/msg01018.php

I've reported the problem to pgsql-hackers with the relevant posts.

/D

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


Re: [pgadmin-hackers] Handling the pg_global of tablespace.

2007-10-11 Thread Dave Page
It should still work for superusers though shouldn't it?

/D

 --- Original Message ---
 From: Hiroshi Saito [EMAIL PROTECTED]
 To: pgadmin-hackers@postgresql.org
 Sent: 11/10/07, 06:01:56
 Subject: [pgadmin-hackers] Handling the pg_global of tablespace.
 
 Hi All.
 
 As for pg_global, handling became difficult for reasons of Ver 8.3 to 
 security.
 http://archives.postgresql.org/pgsql-hackers/2007-10/msg00448.php
 Therefore, we have to do this change by this version.
 
 A method is considered as follows.
 
 1. pg_global is removed by the handling of a tablespace objects.
 or
 2. consideration of statistics and dependents is disregarded. 
 
 I want to convert by 1. 
 Is there any objection? or any idea?
 
 Regards,
 Hiroshi Saito
 
 
 ---(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
 

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


[pgadmin-hackers] Handling the pg_global of tablespace.

2007-10-10 Thread Hiroshi Saito

Hi All.

As for pg_global, handling became difficult for reasons of Ver 8.3 to security.
http://archives.postgresql.org/pgsql-hackers/2007-10/msg00448.php
Therefore, we have to do this change by this version.

A method is considered as follows.

1. pg_global is removed by the handling of a tablespace objects.
or
2. consideration of statistics and dependents is disregarded. 

I want to convert by 1. 
Is there any objection? or any idea?


Regards,
Hiroshi Saito


---(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