John R Pierce <pierce@xxxxxxxxxxxx> writes:
> today has been like deja vu, I'm seeing all kinda postings from
> yesterday regurgitated.
> is this just me? or did the server hiccup and send a lot of stuff twice?
It appears that one alexis.michon@xxxxxxx at athena.ibcp.fr regurgitated
a lot of postings. To judge by what I got this morning (one example
below), the PG servers did reject a lot of them as duplicate, with the
bounce messages going to the original posters, since the regurgitated
messages were complete with forged envelope From :-(. But some of them
apparently got modified enough to escape the duplicate-checksum test,
and then they got posted, since they looked like real messages from
subscribed people.
This happens every so often. It seems to usually be the fault of broken
Microsloth mail software. This particular case doesn't bear enough
traces to be sure about what caused it though.
regards, tom lane
Return-Path: pgsql-performance-owner@xxxxxxxxxxxxxx
Delivery-Date: Fri Jun 10 05:22:23 2011
Received: from mx2.hub.org (mx2.hub.org [200.46.204.254])
by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p5A9MMib014146
for <tgl@xxxxxxxxxxxxx>; Fri, 10 Jun 2011 05:22:23 -0400 (EDT)
Received: from postgresql.org (mail.postgresql.org [200.46.204.86])
by mx2.hub.org (Postfix) with ESMTP id DB0D61752EA1
for <tgl@xxxxxxxxxxxxx>; Fri, 10 Jun 2011 06:22:21 -0300 (ADT)
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Date: Fri, 10 Jun 2011 06:22:22 -0300
From: pgsql-performance-owner@xxxxxxxxxxxxxx
To: Tom Lane <tgl@xxxxxxxxxxxxx>
Subject: Denied post to pgsql-performance
Content-Type: multipart/mixed; boundary="----------=_1307697742-84061-2"
Message-ID: <b6a2bed6fab327f4d7be953df8111f70833e8f43@xxxxxxxxxxxxxx>
This is a multi-part message in MIME format...
------------=_1307697742-84061-2
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Language: en
Your message to the pgsql-performance list has been denied
for the following reason(s):
A message was previous posted with this Message-ID
Duplicate Message-ID - <9435.1307636402@xxxxxxxxxxxxx> (Thu Jun 9 13:20:16 2011)
Duplicate Partial Message Checksum (Thu Jun 9 13:20:16 2011)
------------=_1307697742-84061-2
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Description: Original message
Return-Path: <owner-pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx>
Delivered-To: pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx
Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
by mail.postgresql.org (Postfix) with ESMTP id EA945B5DBEC
for <pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx>; Fri, 10 Jun 2011 06:22:20 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
with ESMTP id 75437-08
for <pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx>;
Fri, 10 Jun 2011 09:22:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from athena.ibcp.fr (athena.ibcp.fr [193.51.160.6])
by mail.postgresql.org (Postfix) with ESMTP id E713DB5DBDB
for <pgsql-performance@xxxxxxxxxxxxxx>; Fri, 10 Jun 2011 06:22:05 -0300 (ADT)
Received: by athena.ibcp.fr (Postfix, from userid 0)
id 3259224C273; Fri, 10 Jun 2011 10:49:48 +0200 (CEST)
Received: from mx1.hub.org (mx1.hub.org [200.46.208.106])
by athena.ibcp.fr (Postfix) with ESMTP id 5ADC424C046
for <alexis.michon@xxxxxxx>; Thu, 9 Jun 2011 18:13:18 +0200 (CEST)
Received: from postgresql.org (mail.postgresql.org [200.46.204.86])
by mx1.hub.org (Postfix) with ESMTP id 7F0F527FE363;
Thu, 9 Jun 2011 13:20:36 -0300 (ADT)
Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
by mail.postgresql.org (Postfix) with ESMTP id 26D77B5DBCB
for <pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx>; Thu, 9 Jun 2011 13:20:16 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024)
with ESMTP id 79164-07
for <pgsql-performance-postgresql.org@xxxxxxxxxxxxxxxxxxx>;
Thu, 9 Jun 2011 16:20:09 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
by mail.postgresql.org (Postfix) with ESMTP id BDC98B5DBC0
for <pgsql-performance@xxxxxxxxxxxxxx>; Thu, 9 Jun 2011 13:20:08 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p59GK2Bu009436;
Thu, 9 Jun 2011 12:20:02 -0400 (EDT)
To: Jochen Erwied <jochen@xxxxxxxxx>
cc: Marti Raudsepp <marti@xxxxxxxxx>,
muthu krishnan <muthu.krishnan.linux@xxxxxxxxx>,
Jochen Erwied <jochen@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
pgsql-performance@xxxxxxxxxxxxxx
In-reply-to: <386582098.20110609125323@xxxxxxxxx>
References: <BANLkTikknfi5L52PuPZuF1Eof1y1qdiY1w@xxxxxxxxxxxxxx> <16710651848.20110609113019@xxxxxxxxx> <BANLkTi=MViJpg21a0-gv0fEx8kg8Zo4z1g@xxxxxxxxxxxxxx> <BANLkTinaGxu-ruoJaPUoCgj5te7HvYSSwA@xxxxxxxxxxxxxx> <386582098.20110609125323@xxxxxxxxx>
Comments: In-reply-to Jochen Erwied <jochen@xxxxxxxxx>
message dated "Thu, 09 Jun 2011 12:53:23 +0200"
Date: Thu, 09 Jun 2011 12:20:02 -0400
Message-ID: <9435.1307636402@xxxxxxxxxxxxx>
From: Tom Lane <tgl@xxxxxxxxxxxxx>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Mailing-List: pgsql-performance
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@xxxxxxxxxxxxxx?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@xxxxxxxxxxxxxx>
List-Post: <mailto:pgsql-performance@xxxxxxxxxxxxxx>
List-Subscribe: <mailto:majordomo@xxxxxxxxxxxxxx?body=sub%20pgsql-performance>
List-Unsubscribe: <mailto:majordomo@xxxxxxxxxxxxxx?body=unsub%20pgsql-performance>
Precedence: bulk
Sender: pgsql-performance-owner@xxxxxxxxxxxxxx
X-IBCP-MailScanner-Information: Please contact the ISP for more information
X-IBCP-MailScanner-ID: 3259224C273.A3A7F
X-IBCP-MailScanner: Found to be clean
X-IBCP-MailScanner-From: root@xxxxxxxxxxxxxx
Subject: Re: [PERFORM] Postgresql on itanium server
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
T_RP_MATCHES_RCVD=-0.01
X-Spam-Level:
Jochen Erwied <jochen@xxxxxxxxx> writes:
> Thursday, June 9, 2011, 12:45:06 PM you wrote:
>> As the URL mentions, you can build with CFLAGS=-ffast-math, that
>> should work for PostgreSQL too.
> I just tried this with the source for 9.0.4, at least with this version the
> build will not complete since there is a check in
> src/backend/utils/adt/date.c throwing an error if FAST_MATH is active.
Yeah. See
http://archives.postgresql.org/pgsql-bugs/2002-09/msg00169.php
and following discussions, which eventually led to adding the #error.
Now this was all done in regards to PG's original floating-point
timestamp implementation. It's possible that in an integer-datetimes
build (which is now the default) we don't need to forbid -ffast-math to
prevent strange datetime results. But nobody's done the work to prove
that, because there isn't any particularly good reason to enable
-ffast-math in a database in the first place. (Other than coping with
brain-dead platforms, I guess.)
However ... I'm not sure I believe that this is related to the OP's
problem anyway. Postgres doesn't normally work with any denormalized
numbers, so the messages he's seeing probably stem from some other sort
of shortcoming in the hardware FP support. It would be interesting to
see specific examples of SQL operations that trigger the kernel message.
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
------------=_1307697742-84061-2--
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
