| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Subject: | Re: Disabling memory display in EXPLAIN ANALYZE |
| Date: | 2018-04-02 21:01:08 |
| Message-ID: | 20180402210108.GA24540@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Andres Freund (andres(at)anarazel(dot)de) wrote:
> i.e. memory consumption differs between environments. Which isn't
> surprising.
>
> I wonder if we could disable the display with a separate switch or tie
> it to !'COSTS OFF && TIMING OFF' or such?
Yeah, I agree with having these suppressed when we're running the
regression tests. I don't particularly care for having them suppressed
under either costs or timing off though, as those are really pretty
specific and independnet flags. Perhaps what we need is a flag that
says 'regression mode'...
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2018-04-02 21:04:47 | Re: [PATCH] Logical decoding of TRUNCATE |
| Previous Message | Stephen Frost | 2018-04-02 20:58:08 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |