pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Fuhr <mike@fuhr.org>
To: Donald Fraser <postgres@kiwi-fraser.net>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: Notifications
Date: Thu, 16 Dec 2004 11:54:26 -0700
Message-ID: <20041216185426.GA80816@winnie.fuhr.org> (raw)
In-Reply-To: <003701c4e396$d9b4a270$6464a8c0@DonAcer>
References: <002e01c4e37a$5ab3bae0$6464a8c0@DonAcer>
	<20041216170721.GA67633@winnie.fuhr.org>
	<003701c4e396$d9b4a270$6464a8c0@DonAcer>

On Thu, Dec 16, 2004 at 05:44:09PM -0000, Donald Fraser wrote:
> 
> Ok the problem is that outside our local network, and more precise on the 
> outside of our firewall, users do not receive NOTIFY messages. The exact 
> same software running on the local network, albeit not using SSL does 
> receive NOTIFY messages.

As with the inside-vs-outside issue, SSL might be a red herring.
It's curious that the same software behaves differently in different
locations, but be careful not to use tunnel vision when investigating
the cause.

Is there *anything* else that's different between the systems whose
connections work and those whose don't?

Is it possible that the outside users are connecting to a different
database server than the inside users?

What OS are you using, what language, what database interface?  How
are you checking for NOTIFY messages?

> The problem is immediate, I can instanciate the sending of a NOTIFY message 
> from my own connection and I don't receive a return message yet users on 
> the local network do.

Have you done simple tests with psql?  You'd probably have to issue
a query before seeing the notification, but that should still tell
you if the notification arrived at all.

> Basically now that I know NOTIFY uses TCP and therefore "should" clearly 
> not be getting lost anywhere, I will do a lot more investigating into our 
> software as that is the most likely place for the proble!. It just seems a 
> bit strange that the same software can receive messages when on the local 
> network... The one thing I can be sure of is that it will be software! I 
> think the clue must be the setting up of SSL on our software....

Again, beware of putting on blinders.  If the database connection
is otherwise working then it would be strange if SSL configuration
were causing the problem.  *Is* the connection otherwise working?

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/



view thread (10+ messages)  latest in thread

Message-ID: <20041216185426.GA80816@winnie.fuhr.org>
Permalink:  ../20041216185426.GA80816@winnie.fuhr.org/
Also on:    postgresql.org/message-id/20041216185426.GA80816@winnie.fuhr.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mike@fuhr.org, postgres@kiwi-fraser.net
  Subject: Re: Notifications
  In-Reply-To: <20041216185426.GA80816@winnie.fuhr.org>
  References: <002e01c4e37a$5ab3bae0$6464a8c0@DonAcer> <20041216170721.GA67633@winnie.fuhr.org> <003701c4e396$d9b4a270$6464a8c0@DonAcer> <20041216185426.GA80816@winnie.fuhr.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox