From: Michael Stone <mstone+postgres@mathom.us>
To: pgsql-performance@postgresql.org
Subject: Re: File Systems Compared
Date: Wed, 06 Dec 2006 13:11:53 -0500
Message-ID: <20061206181151.GC20976@mathom.us> (raw)
In-Reply-To: <457704F0.10004@freesurf.fr>
References: <BEB285F8-0BD2-4524-BD46-B1D35E7EFBEB@clickspace.com>
<25B4661C-C66A-4DE4-AD8A-A911353914BC@purefiction.net>
<4576F045.3080400@bluegap.ch>
<20061206164338.GA16573@uio.no>
<457701D4.3070803@bluegap.ch>
<457704F0.10004@freesurf.fr>
On Wed, Dec 06, 2006 at 06:59:12PM +0100, Arnaud Lesauvage wrote:
>Markus Schiltknecht a écrit :
>>What's common practice? What's it on the pgsql mailing lists?
>
>The netiquette usually advise mailers to wrap after 72 characters
>on mailing lists.
>This does not apply for format=flowed I guess (that's the format
>used in Steinar's message).
It would apply to either; format=flowed can be wrapped at the receiver's
end, but still be formatted to a particular column for readers that
don't understand format=flowed. (Which is likely to be many, since
that's a standard that never really took off.) No wrap netiquette
applies to formatted text blocks which are unreadable if wrapped (such
as bonnie or EXPLAIN output).
Mike Stone
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: pgsql-performance@postgresql.org
Cc: mstone+postgres@mathom.us
Subject: Re: File Systems Compared
In-Reply-To: <20061206181151.GC20976@mathom.us>
* 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