Re: [pgadmin-support] pgadmin 8.3 beta 5: ERROR: permission denied for tablespace pg_default

2007-09-16 Thread Harald Armin Massa 
Dave,

> According to the words of Master Tom in
> > http://svr5.postgresql.org/pgsql-hackers/2004-06/msg00947.php,
> > " Joe User probably shouldn't be fooling with tablespaces at all."
>
> Gah - so you can use it despite having no permissions on it if you don't
> specify it? On what planet does that seem sane?


As much as I understood, pg_default is not necessarly the default
tablespace??? But I never fiddled with tablespaces up to now :)

But if your theorie is correct, then that sanity or not is buried deep
within Postgres ... I am very sure that I am using the default win32 build.

>
> I guess I'll have to on the CREATE version of the dialogs. Thankfully,
> it shouldn't matter for the ALTER versions as they only script the
> tabespace if you try to change it.


Sounds fine.

Harald

-- 
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
fx 01212-5-13695179
-
EuroPython 2008 will take place in Vilnius, Lithuania - Stay tuned!

Re: [pgadmin-support] pgadmin 8.3 beta 5: ERROR: permission denied for tablespace pg_default

2007-09-16 Thread Erwin Brandstetter 
Hi Harald!

On Sep 16, 8:56 pm, [EMAIL PROTECTED] ("Harald Armin Massa")
wrote:
> As much as I understood, pg_default is not necessarly the default
> tablespace??? But I never fiddled with tablespaces up to now :)

I have summed up which tablespace pg uses here:
   http://archives.postgresql.org/pgadmin-hackers/2007-09/msg00051.php

Regards
Erwin


---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org

Re: [pgadmin-support] pgadmin 8.3 beta 5: ERROR: permission denied for tablespace pg_default

2007-09-16 Thread Erwin Brandstetter 
On Sep 15, 10:43 am, [EMAIL PROTECTED] (Dave Page) wrote:
> Harald Armin Massa wrote:
> > Hello,
>
> > it may or may not be considered as a pgadmin error:
>
> > I try to create an index on a column of a table. Using the
> > pgadmin-wizard, that results in:
>
> > CREATE INDEX otformularkopf_test
> >ON otformularkopf (id_pkfk)
> >TABLESPACE pg_default;
>
> > with NO chance to get rid of the "   TABLESPACE pg_default" clause;
> > so I am stuck with "ERROR: permission denied for tablespace pg_default"
>
> > According to the words of Master Tom in
> >http://svr5.postgresql.org/pgsql-hackers/2004-06/msg00947.php,
> > " Joe User probably shouldn't be fooling with tablespaces at all."
>
> Gah - so you can use it despite having no permissions on it if you don't
> specify it? On what planet does that seem sane?


Unfortunately it affects ALTER cases as well. And there is nothing
pgAdmin even _could_ do about that.
Say, a user has CREATE rights on tablespace foo. He moves a table
there (or creates it there).
   ALTER TABLE test SET TABLESPACE foo;

But later he is unhappy with the results. So he tries to move it back
where it came from: to pg_default, but he cannot!
   ALTER TABLE test SET TABLESPACE pg_default;

In my book that's listed under "postgres bug", not under "sane". In
practice an admin has to explicitly grant CREATE rights on pg_default
along with any CREATE rights on any tablespace, or it will be a one
way trip. How many admins would think of that or even know it?



Regards
Erwin


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

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