Re: effective_io_concurrency's steampunk spindle maths

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: effective_io_concurrency's steampunk spindle maths
Date: 2020-03-06 20:07:45
Message-ID: 18806.1583525265@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> So I think we should either rename e_i_c or keep it as is, and then also
> have a new GUC. And then translate the values between those (but that
> might be overkill).

Please DON'T try to have two interrelated GUCs for this. We learned
our lesson about that years ago.

I think dropping the existing GUC is a perfectly sane thing to do,
if the new definition wouldn't be compatible. In practice few
people will notice, because few will have set it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2020-03-06 20:52:02 Re: effective_io_concurrency's steampunk spindle maths
Previous Message Tom Lane 2020-03-06 20:04:27 Re: More tests to stress directly checksum_impl.h