Ancient messages regurgitated into pgsql-admin, again

This is the second time in the past few days that lechlecha.jct.ac.il
has injected a bunch of old messages into pgsql-admin.  Can you arrange
to blacklist that machine so it doesn't happen again?

One example attached, but there were about two dozen this morning.

            regards, tom lane

------- Forwarded Message

Return-Path: pgsql-admin-owner+M20546@postgresql.org
Delivery-Date: Fri Feb 10 21:06:47 2006
Received: from ams.hub.org (ams.hub.org [200.46.204.13])
    by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k1B26k0C004058
    for <tgl@sss.pgh.pa.us>; Fri, 10 Feb 2006 21:06:47 -0500 (EST)
Received: from postgresql.org (postgresql.org [200.46.204.71])
    by ams.hub.org (Postfix) with ESMTP id C322A67B446
    for <tgl@sss.pgh.pa.us>; Fri, 10 Feb 2006 22:06:46 -0400 (AST)
X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
    by postgresql.org (Postfix) with ESMTP id 32DFF9DCC03
    for <pgsql-admin-postgresql.org@localhost.postgresql.org>; Mon,  6 Feb 2006 04:09:24 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
 by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
 with ESMTP id 04109-01-5
 for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
 Mon,  6 Feb 2006 04:09:22 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from lechlecha.jct.ac.il (lechlecha.jct.ac.il [147.161.1.247])
    by postgresql.org (Postfix) with ESMTP id D9BC59DCBC5
    for <pgsql-admin@postgresql.org>; Mon,  6 Feb 2006 04:09:16 -0400 (AST)
Received: from lechlecha.jct.ac.il (lechlecha.jct.ac.il [127.0.0.1])
    by localhost (Postfix) with ESMTP
    id 8E6492344A3; Mon,  6 Feb 2006 10:08:20 +0200 (IST)
Received: from ketubot.jct.ac.il (ketubot.jct.ac.il [147.161.37.128])
    by lechlecha.jct.ac.il (Postfix) with ESMTP
    id 7225E2344C1; Mon,  6 Feb 2006 10:08:20 +0200 (IST)
Received: from ketubot.jct.ac.il (localhost [127.0.0.1])
    by ketubot.jct.ac.il (8.12.10+Sun/8.12.10) with ESMTP id k1689HwB002730;
    Mon, 6 Feb 2006 10:09:17 +0200 (IST)
Received: (from tsurkin@localhost)
    by ketubot.jct.ac.il (8.12.10+Sun/8.12.9/Submit) id k1689HGw002729;
    Mon, 6 Feb 2006 10:09:17 +0200 (IST)
Received: from lechlecha.jct.ac.il (lechlecha.jct.ac.il [147.161.1.247])
    by demai.jct.ac.il (8.12.11/8.12.11) with ESMTP id j5SGYJ4a001612
    for <tsurkin@mail.jct.ac.il>; Tue, 28 Jun 2005 19:34:19 +0300
Received: from lechlecha.jct.ac.il (lechlecha.jct.ac.il [127.0.0.1])
    by localhost (Postfix) with ESMTP id 19979234231
    for <tsurkin@mail.jct.ac.il>; Tue, 28 Jun 2005 18:22:56 +0300 (IDT)
Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159])
    by lechlecha.jct.ac.il (Postfix) with ESMTP id B7A1E2341E0
    for <tsurkin@mail.jct.ac.il>; Tue, 28 Jun 2005 18:22:55 +0300 (IDT)
Received: from postgresql.org (svr1.postgresql.org [200.46.204.71])
    by svr4.postgresql.org (Postfix) with ESMTP id 93A945AF9C1;
    Tue, 28 Jun 2005 16:33:46 +0000 (GMT)
X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
    by svr1.postgresql.org (Postfix) with ESMTP id 1B295529D6
    for <pgsql-admin-postgresql.org@localhost.postgresql.org>; Tue, 28 Jun 2005 12:41:43 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
 by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
 with ESMTP id 57336-06
 for <pgsql-admin-postgresql.org@localhost.postgresql.org>;
 Tue, 28 Jun 2005 15:41:39 +0000 (GMT)
Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25])
    by svr1.postgresql.org (Postfix) with ESMTP id 370DA529C6
    for <pgsql-admin@postgresql.org>; Tue, 28 Jun 2005 12:41:35 -0300 (ADT)
Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944
Received: from state.g2switchworks.com by mail.g2switchworks.com; 28 Jun 2005 10:41:33 -0500
Subject: Re: [ADMIN] How to compare the schemas ?
From: Scott Marlowe <smarlowe@g2switchworks.com>
To: tsirkin@gmail.com
Cc: Peter Eisentraut <peter_e@gmx.net>,
        Milorad Poluga <milorad.poluga@cores.co.yu>,
        pgsql-admin@postgresql.org
In-Reply-To: <E1DnGCE-0000ps-Rv@hetzner.co.za>
References: <E1DnGCE-0000ps-Rv@hetzner.co.za>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1119973293.8208.107.camel@state.g2switchworks.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2)
Date: Tue, 28 Jun 2005 10:41:33 -0500
X-Virus-Scanned: by amavisd-new at hub.org
X-Mailing-List: pgsql-admin
Precedence: bulk
Status: RO
X-Status:
X-Keywords:
X-UID: 47182
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=1.224 required=5 tests=[AWL=-0.928,
 RCVD_IN_WHOIS_INVALID=2.151, UNPARSEABLE_RELAY=0.001]
X-Spam-Score: 1.224
X-Spam-Level: *
X-Mailing-List: pgsql-admin
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Tue, 2005-06-28 at 08:32, Ian FREISLICH wrote:
> Peter Eisentraut wrote:
> > Milorad Poluga wrote:
> > > One (certainly not the best options) is to do something like this:
> > >
> > > pg_dump ... DB1 =A0> PG_SCHEMA1
> > > pg_dump ... DB2 =A0> PG_SCHEMA2
> > > diff =A0PG_SCHEMA1 =A0PG_SCHEMA2 =A0> differences.txt
> >
> > What is wrong with that?
>
> All the extra TOC ID and comment stuff that pg_dump introduces.
> Also, I think that the dump is sorted by creation order or some
> other scheme, so even though the databases might be identical, the
> diff output would be significant.
>
> This is something that I have battled in the past.  The only solution
> was to always update the database from a set of scripts, one for
> each function and one for the tables.  These scripts kept in CVS
> auto update the comment on each object:
>
> COMMENT ON FUNCTION namedConfGen(TEXT,TEXT) IS '$Id: sproc.api.namedConfGen,v 1.
> 8 2004/05/07 08:02:55 ianf Exp $';
>
> Now I can cvs diff using the version numbers.  Not ideal, but at
> least I know exactly where I am.

I just pass a schema backup through grep or sed with this option:

grep -Pv "^--"

and get a pretty good idea of the differences.

Since our databases are created by scripts as well, they generally share
creation order and such, so any small difference from missing a script
on one or another environment shows up with this.

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

------- End of Forwarded Message