Thread: locally running servers

locally running servers

From
Miha Radej
Date:
hi!

i noticed that pgadmin found i have a server running on the same machine 
and it automatically added it to the object browser. the first few times 
it also reported an error about not being able to read the pgsql key 
from the registry but it still added the server to the list, now it just 
adds it even if i delete it. could there be an option where pgadmin 
would list any servers it can find and i could then check which i'd like 
to see at startup, even if i or any other user accidentally deletes 
them? or if i could just turn off this feature of automatically adding 
the server to the list?
thank you :)

-- 
regards,
Miha



Re: locally running servers

From
Andreas Pflug
Date:
Miha Radej wrote:
> hi!
> 
> i noticed that pgadmin found i have a server running on the same machine 
> and it automatically added it to the object browser. the first few times 
> it also reported an error about not being able to read the pgsql key 
> from the registry but it still added the server to the list, now it just 
> adds it even if i delete it. could there be an option where pgadmin 
> would list any servers it can find and i could then check which i'd like 
> to see at startup, even if i or any other user accidentally deletes 
> them? or if i could just turn off this feature of automatically adding 
> the server to the list?

I wonder why you wouldn't like to see the server on your very own 
machine. I'm not too inclined to change the detection feature (the 
missing key could come from an older pginstaller, what's the exact key?)

Regards,
Andreas


Re: locally running servers

From
Miha Radej
Date:
if i set up pgadmin for certain users and set only those servers they 
need. and if (unfortunately) a server is running on the same machine, i 
do not wish for it to be on the list unless i specify it.

the problematic key was:
HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Services\pgsql-8.0-beta1
this key exists (and existed when the error was reported). if i remember 
correctly, there was something about a missing file in the error i got. 
in this key i have the following data stored: data dir, superuser, 
display name, encoding, locale and service account.

regards,
M


Andreas Pflug wrote:
> Miha Radej wrote:
> 
>> hi!
>>
>> i noticed that pgadmin found i have a server running on the same 
>> machine and it automatically added it to the object browser. the first 
>> few times it also reported an error about not being able to read the 
>> pgsql key from the registry but it still added the server to the list, 
>> now it just adds it even if i delete it. could there be an option 
>> where pgadmin would list any servers it can find and i could then 
>> check which i'd like to see at startup, even if i or any other user 
>> accidentally deletes them? or if i could just turn off this feature of 
>> automatically adding the server to the list?
> 
> 
> I wonder why you wouldn't like to see the server on your very own 
> machine. I'm not too inclined to change the detection feature (the 
> missing key could come from an older pginstaller, what's the exact key?)
> 
> Regards,
> Andreas
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
>               http://www.postgresql.org/docs/faqs/FAQ.html
> 



Re: locally running servers

From
Andreas Pflug
Date:
Miha Radej wrote:
> if i set up pgadmin for certain users and set only those servers they 
> need. and if (unfortunately) a server is running on the same machine, i 
> do not wish for it to be on the list unless i specify it.

This requirement appears quite exotic to me. I don't see how to prevent 
discovering it for you without degrading the usefulness of the feature 
for others.
Of course you could edit the server entry; autodiscovery won't override 
settings for a server with a ServiceId already stored.

Regards,
Andreas


Re: locally running servers

From
Miha Radej
Date:
Andreas Pflug wrote:
> This requirement appears quite exotic to me. I don't see how to prevent 
> discovering it for you without degrading the usefulness of the feature 
> for others.

perhaps if there were an option somewhere, like "disable server 
autodiscovery at startup", which would be enabled by default?

oh well :) i'll stop complaining now :)

regards,
Miha