I semi-regularly get emails that appear in the message list fine (From,
Subject, Date fields populated ), but that 'appear' to be empty
( preview pane is blank and opening the email results in an empty
'viewer' ). The emails are not empty -- viewing the email in another
client provides the full text of said emails. I'm not sure if the issue
is that in some cases evo is not downloading/storing the body of the
email (i'm using OWA ) or if evo is failing on the rendering of the
email. Sorta hoping it's the former and that there's a quick/easy way
to get evo to download said email again.
I saved an example message that exhibits this issue for me using evo's
'save as mbox' functionality. It's attached -- the body of the email is
missing.
Here is the email source taken from mutt:
$ cat cur/1285764408.11663_116.raker\:2\,S
Received: from mailblocker.ateb.com ([172.16.48.222]) by sr002-2k3exc.ateb.com with Microsoft
SMTPSVC(6.0.3790.4675);
Wed, 29 Sep 2010 05:53:22 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvcBAOOookzILtBqkWdsb2JhbACDHZ5+FQEBAQEJCwoHEQMftCU8ghcBBZANAQSBIoMudI09
X-IronPort-AV: E=Sophos;i="4.57,252,1283745600";
d="scan'208";a="6990640"
Received: from mx1.hub.org ([200.46.208.106])
by mailblocker.ateb.com with ESMTP; 29 Sep 2010 05:53:21 -0400
Received: from postgresql.org (mail.postgresql.org [200.46.204.86])
by mx1.hub.org (Postfix) with ESMTP id 5C671326760A;
Wed, 29 Sep 2010 09:53:19 +0000 (UTC)
Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
by mail.postgresql.org (Postfix) with ESMTP id 29B0F1336FA7
for <pgsql-general-postgresql org mail postgresql org>; Wed, 29 Sep 2010 06:52:54 -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 48091-09
for <pgsql-general-postgresql org mail postgresql org>;
Wed, 29 Sep 2010 09:52:48 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from web29017.mail.ird.yahoo.com (web29017.mail.ird.yahoo.com [212.82.110.163])
by mail.postgresql.org (Postfix) with SMTP id 7669C1336971
for <pgsql-general postgresql org>; Wed, 29 Sep 2010 06:52:45 -0300 (ADT)
Received: (qmail 4544 invoked by uid 60001); 29 Sep 2010 09:52:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s1024; t=1285753965;
bh=bt6qyE2Sa5Nzv6I5P72mA5Xc/1nA/KgLISPI7Z7/Gig=;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
b=EgzfR+3lPMjRNOh6OqDhRBe7lGv3fKX4vOysxeSEtWXcDKNXcbubwbA2ZPTo1qJmtYXPzt2LvgbaJ+rtCG2Udcqcw8gmy6/oEDQNi5Ad+4qXEzzu6S7BfXQGMGWSCeuLHfwSHxB9RGulVh9yM7FakYHGEVkyR0FebXOuI1cpGrc=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.it;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
b=YToSHlZPEDO/NPc6vepZNNF2xH2bpBKMZ4oC48U3Oa1twt7vf+E+HfFFbkzc/Y4KwBbEBfayKS4jB+i0EsqdXF4y4FdImvJRIUhzPkVOBkp0d+Zjnb+1lkenCjb+LMKXUqqGE2B/szkBWfhNqSw58uNPbgV6KsC6t+sy/kUk9yg=;
Message-ID: <165530 4179 qm web29017 mail ird yahoo com>
X-YMail-OSG: jqLQYicVM1n6QRk28r1cZtuZxhHAphHh.qsoEZjHoWxktMU
PgbzKHICRZtXILtg5tWba0Jc_Pqx9gJjAaMyuqufxAWMwGuI59MHOa5X6Dvt
usAxkf3U9E6EMYd1mnIO7Qn5daArKY9cmSEdIHCao92D3b4Wfp5M47Jb5kOG
pp69mrFF3I8mMH7oxpcBE6zMwnV9z1N5MmRB_hUSJ40BIpttoAosgfTU-
Received: from [85.33.62.89] by web29017.mail.ird.yahoo.com via HTTP; Wed, 29 Sep 2010 09:52:45 GMT
X-Mailer: YahooMailRC/497 YahooMailWebService/0.8.105.279950
Date: Wed, 29 Sep 2010 09:52:45 +0000 (GMT)
From: Leonardo Francalanci <m_lists yahoo it>
Subject: [GENERAL] Postgresql for a CEP app
To: pgsql-general <pgsql-general postgresql org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9
X-Spam-Level:
X-Mailing-List: pgsql-general
List-Archive: <http://archives.postgresql.org/pgsql-general>
List-Help: <mailto:majordomo postgresql org?body=help>
List-ID: <pgsql-general.postgresql.org>
List-Owner: <mailto:pgsql-general-owner postgresql org>
List-Post: <mailto:pgsql-general postgresql org>
List-Subscribe: <mailto:majordomo postgresql org?body=sub%20pgsql-general>
List-Unsubscribe: <mailto:majordomo postgresql org?body=unsub%20pgsql-general>
Precedence: bulk
Sender: pgsql-general-owner postgresql org
Return-Path: pgsql-general-owner+M167801 postgresql org
X-OriginalArrivalTime: 29 Sep 2010 09:53:22.0219 (UTC) FILETIME=[26F3BFB0:01CB5FBC]
Content-Length: 1493
Lines: 43
Hi,
I need to generate aggregates of data coming from a stream.
I could easily doing it inserting data coming from the stream into a table,
and then query it using something like:
select <my aggregation function> from atable group by <a column list>
The problem with this approach is that I would have to wait for the whole
stream to be finished before making the above query; since we're talking
about 20M+ rows, it would take some time for the query to finish.
What if I do something like:
select <my aggregation function> from my_fifo_function([...])=20
group by <a column list>
where my_fifo_function reads data from the stream and returns "rows" as
soon as they are available on the stream? This way I would get the reply
as soon as the stream has finished (assuming postgresql can keep up
with that). In other words, the query would be made even before the
stream has "started", and would last at least as long as the stream.
(of course, I don't need data from the stream to be saved in any way,
that's why I don't need to store it in any table).
Does postgresql read data from a function returning a SETOF row by row?
Or it waits the whole function to be finished (caching the whole resultset)
before starting to use the returned data? If it reads row by row I think it
could work...
Would that make sense?=20
--=20
Sent via pgsql-general mailing list (pgsql-general postgresql org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Attachment:
[GENERAL]PostgresqlforaCEPapp.mbox
Description: application/mbox