| From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: TAP tests take a long time |
| Date: | 2017-04-12 02:39:22 |
| Message-ID: | CAMsr+YH9jMWG-evFY2msZtgHrZk36f93E-YcVYAvtoeLnHiy-g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12 April 2017 at 08:22, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
> On Wed, Apr 12, 2017 at 9:12 AM, Craig Ringer
> <craig(dot)ringer(at)2ndquadrant(dot)com> wrote:
>>
>> We should also have a debug --no-fsync option for initdb, or maybe allow it
>> to take -o options to pass to child postgres so we can pass fsync=off .
>
> That's an idea as well...
OK, looking at this, initdb already runs postgres -F then does its own
fsync()s at the end.
It already has a -N / --no-sync option too. Which is already used by
PostgresNode.pm . So as much as can be done has already been done
here.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-04-12 02:48:46 | Re: TAP tests take a long time |
| Previous Message | Noah Misch | 2017-04-12 02:27:39 | Re: error handling in RegisterBackgroundWorker |