Re: Handling the pg_global of tablespace.

It should still work for superusers though shouldn't it?

/D

> ------- Original Message -------
> From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
> To: pgadmin-hackers(at)postgresql(dot)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
>