| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: Why do pg_upgrade's test use the serial schedule? |
| Date: | 2018-11-06 00:24:57 |
| Message-ID: | 20181106002457.GC1814@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 05, 2018 at 02:11:42PM -0800, Andres Freund wrote:
> Because just about everything else taking substantial time already
> disables it. pg_regress forks off a postmaster with -F, the tap tests do
> so for large portions via fsync=off in the config (c.f. PostgresNode.pm).
And in most cases people will forget to set up TEMP_CONFIG when setting
up a new environment. If it is possible to reduce the I/O traffic when
running check-world by default and if we are able to make it faster with
a parallel schedule, my take is to do by default instead of expecting
the user to set up that all the time. That's less to think about.
So I am +1 and +1 for Andres' suggestions on this thread.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas 'ads' Scherbaum | 2018-11-06 00:41:15 | Re: [PATCH] Improvements to "Getting started" tutorial for Google Code-in task |
| Previous Message | Amit Langote | 2018-11-06 00:23:22 | Re: Getting ERROR: could not open file "base/13164/t3_16388" with partition table with ON COMMIT |