| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mingwei Jia <i(at)nayishan(dot)top>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [RFC PATCH v2 RESEND 10/10] umbra: add patch 9 compactor framework and non-interference policy |
| Date: | 2026-06-02 14:13:45 |
| Message-ID: | CA+TgmoZTmyCoKQ8XbMceJCt0a7hbMH-UHwEZE3PznuHZ7Y9QAQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 1, 2026 at 7:45 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This is still not working :-(.
>
> One patch per email is not very useful: our cfbot is not smart enough
> to realize that this is meant as a set of patches rather than a series
> of updated versions of a single patch.
>
> Also, I'm not quite sure what you are doing but it is not ending up as
> an attached file. It really needs to be an attachment, not inline
> text, so that it can be conveniently saved and won't get mangled by
> anyone's mail reader.
>
> You could make it work by attaching several patch files to one email.
> But for a patch set as large as this, it's probably a better idea
> to put the patch files into a tar.gz file and send that as a single
> attachment.
Also, each patch will need a real commit message explaining its
purpose in detail. Like our actual commit messages.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-06-02 14:48:11 | Re: Broken build on macOS (Universal / Intel): cpuid instruction not available |
| Previous Message | Henson Choi | 2026-06-02 14:11:05 | Re: Row pattern recognition |