Re: Find all running postgres DB servers on a network

From: Frederiko Costa <frederiko(at)gmail(dot)com>
To: ojas dubey <ojas(dot)dubey(at)gmail(dot)com>
Cc: Rich <rhdyes(at)gmail(dot)com>, Scott Whitney <swhitney(at)journyx(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Find all running postgres DB servers on a network
Date: 2010-11-18 17:10:58
Message-ID: AANLkTimqufir3iK4UzMzZkz6ktMn6Z4gEh+SDyayau6x@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

I believe in this case you will have to talk with the sysadmin and have an
agreement about this requirement for your application. I don't know about
Spiceworks, but I see nmap as an application working on layer 3/4, so you
may be subject to firewall rules or anything defined in the security policy.

~Fred

On Thu, Nov 18, 2010 at 7:26 AM, ojas dubey <ojas(dot)dubey(at)gmail(dot)com> wrote:

> Thank you Rich,Fred,Scott,Viktor and Gerard for your replies.
>
> Actually I am neither the system administrator nor the person who set up
> all the servers. I am developing an application which would provide the user
> with a list of running Postgres DB servers from which the user can select
> one. So I was wondering if scanning ports using nmap or Spiceworks would
> get me into trouble with the System administrator for trying to flood the
> network with my requests or not ?
>
> Regards,
> Ojas
>
>
> On Thu, Nov 18, 2010 at 2:51 AM, Rich <rhdyes(at)gmail(dot)com> wrote:
>
>> Use nmap. Unless you deliberately changed the IP port you should have no
>> problem. Are you the one who setup all the servers?
>>
>>
>> On Wed, Nov 17, 2010 at 4:03 PM, Frederiko Costa <frederiko(at)gmail(dot)com>wrote:
>>
>>> True. However, I was just assuming that Postgres was running on default
>>> ports. If not, you could also probe in port ranges or even probe the network
>>> for open ports to have an idea and get closer. It might be faster option if
>>> software such as Spiceworks is not being used.
>>>
>>> Spiceworks looks a good option too.
>>>
>>> ~Fred
>>>
>>>
>>> On Wed, Nov 17, 2010 at 12:56 PM, Scott Whitney <scott(at)journyx(dot)com>wrote:
>>>
>>>> That only works in the event that you have PG listening on port 5432.
>>>>
>>>> A product like Spiceworks will provide much more detail, presuming you
>>>> have the IT credentials to talk to the machines.
>>>>
>>>> ------------------------------
>>>>
>>>> nmap is the way to go. Try to scan for port 5432 in a range of IP of
>>>> your
>>>> LAN.
>>>>
>>>> ~Fred
>>>> Linkedin profile: http://www.linkedin.com/in/frederikocosta
>>>>
>>>>
>>>> On Sun, Nov 14, 2010 at 8:52 AM, ojas dubey <ojas(dot)dubey(at)gmail(dot)com>
>>>> wrote:
>>>>
>>>> > Hi,
>>>> >
>>>> > I wanted to know if there is a way to get the hostnames of all the
>>>> systems
>>>> > running PostGres DB servers on a local network on Windows (XP/Vista/7)
>>>> using
>>>> > JDBC or any other Java API ?
>>>> >
>>>> >
>>>> > Regards,
>>>> > Ojas
>>>> >
>>>>
>>>>
>>>>
>>>
>>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Wells Oliver 2010-11-18 17:42:49 8.4 process killed- what sort of recovery options do I have?
Previous Message ojas dubey 2010-11-18 15:26:38 Re: Find all running postgres DB servers on a network