public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Tom Lane <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: Problems with pgsql-announce
Date: Fri, 12 Jan 2007 16:18:57 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Fri, Jan 12, 2007 at 10:08:51AM -0500, Tom Lane wrote:
> Magnus Hagander <[email protected]> writes:
> >> most of what gets 'falsely stuck' tend to be 
> >> subscribe/unsubscribe requests though ... if you see one that has been 
> >> 'spending 48 hours', please forward it to me with full headers, as something
> >> else is wrong ...
> 
> > I've definitly seen that happen and more than once. DOn't have one
> > around, but I'll eb sure to collect the headers next time it happens.
> 
> Something else I've noticed saveral times in the last week is getting a
> delayed copy of something that already came through.  These weren't the
> usual newbie-sends-another-copy-after-subscribing deal because they came
> from established subscribers.  I didn't save copies but will next time.

I'm glad it's not just me. I've noticed this a couple of times, but
didn't have time to investigate at the time either - I thought it might
be my new MUA on the cellphone acting up ;-)

//Magnus

view thread (18+ messages)  latest in thread

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Problems with pgsql-announce
  In-Reply-To: <[email protected]>

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

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