| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Greg Stark <stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Recovery Test Framework |
| Date: | 2009-01-13 01:12:46 |
| Message-ID: | 15178.1231809166@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Tom Lane wrote:
>> David Fetter <david(at)fetter(dot)org> writes:
>>> 1. Remove the messages size limits on -hackers. They serve no useful
>>> purpose, and they interfere with our development process.
>>
>> Agreed, or at least boost it up a good bit more.
> the question really is how much "a bit more" is - right now the limit is
> 100000 characters which limits us to ~70KB of attachments (around the
> size of the Hot-standby patch if bzip2 compressed).
> The SE-Postgres patch for example is ~650KB uncompressed - if we want to
> cope with uncompressed patches that large we would have to increase
> the current limit by a factor of 10 at least.
I feel no need to encourage people to send huge patches uncompressed ;-)
gzip normally gets at least 3x or 4x on large diffs. So a limit around
250K ought to be enough.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-01-13 01:15:49 | Re: Recovery Test Framework |
| Previous Message | Bruce Momjian | 2009-01-13 00:54:43 | Re: Documenting pglesslog |