Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16109: Postgres planning time is high across version (Expose buffer usage during planning in EXPLAIN)
Date: 2020-03-31 01:31:46
Message-ID: 20200331013146.GA14618@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Jan 29, 2020 at 12:15:59PM +0100, Julien Rouhaud wrote:
> Rebase due to conflict with 3ec20c7091e97.

This is failing to apply probably since 4a539a25ebfc48329fd656a95f3c1eb2cda38af3.
Could you rebase? (Also, not sure if this can be set as RFC?)

--
Justin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Justin Pryzby 2020-03-31 03:10:53 translation typos
Previous Message Fan Liu 2020-03-31 01:24:13 RE: why wal_max_size does not work?

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-03-31 01:40:07 Very outdated comments in heapam_index_build_range_scan.
Previous Message Fujii Masao 2020-03-31 01:16:03 Re: pgsql: Improve handling of parameter differences in physical replicatio