From: Julien Rouhaud <rjuju123@gmail.com>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: BUFFERS enabled by default in EXPLAIN (ANALYZE)
Date: Tue, 18 Jan 2022 14:53:09 +0800
Message-ID: <20220118065309.owxcnfpldwo6dbpz@jrouhaud> (raw)
In-Reply-To: <20211202005820.GJ17618@telsasoft.com>
References: <CANNMO++=LrJ4upoeydZhbmpd_ZgZjrTLueKSrivn6xmb=yFwQw@mail.gmail.com>
<20211115190954.GO17618@telsasoft.com>
<20211202005820.GJ17618@telsasoft.com>
Hi,
On Wed, Dec 01, 2021 at 06:58:20PM -0600, Justin Pryzby wrote:
>
> The attached patch series now looks like this (some minor patches are not
> included in this list):
This version of the patchset doesn't apply anymore:
http://cfbot.cputube.org/patch_36_3409.log
=== Applying patches on top of PostgreSQL commit ID 4483b2cf29bfe8091b721756928ccbe31c5c8e14 ===
=== applying patch ./0003-Make-explain-default-to-BUFFERS-TRUE.patch
patching file doc/src/sgml/config.sgml
Hunk #1 FAILED at 7615.
1 out of 1 hunk FAILED -- saving rejects to file doc/src/sgml/config.sgml.rej
By the way, could you add versionning to the patchsets you send, e.g. git
format-patch -vXXX. It would make it easier to know which version are used or
discussed.
I'm switching the CF entry to Waiting on Author.
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-hackers@postgresql.org
Cc: rjuju123@gmail.com, pryzby@telsasoft.com, samokhvalov@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: BUFFERS enabled by default in EXPLAIN (ANALYZE)
In-Reply-To: <20220118065309.owxcnfpldwo6dbpz@jrouhaud>
* 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