| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| 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 22:03:28 |
| Message-ID: | 20180402220328.y3fr5doyck5qtez5@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-04-02 17:01:08 -0400, Stephen Frost wrote:
> * 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.
We already put a number of loosely related things in there, so I don't
think that'd be that weird to continue along those lines.
> Perhaps what we need is a flag that says 'regression mode'...
DWIM mode? reproducible mode?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthony Iliopoulos | 2018-04-02 23:05:44 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Tom Lane | 2018-04-02 21:43:54 | Re: Rethinking -L switch handling and construction of LDFLAGS |