| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Idea for improving buildfarm robustness |
| Date: | 2015-10-01 04:02:19 |
| Message-ID: | 560CB04B.3080704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
So, testing:
1. I tested running an AWS instance (Ubuntu 14.04) into 100% IOWAIT, and
the shutdown didn't kick in even when storage went full "d" state. It's
possible that other kinds of remote storage failures would cause a
shutdown, but don't we want them to?
2. I tested deleting /pgdata/* several times (with pgbench running), and
Postgres shut down within 20 seconds each time.
3. I tested messing with the permissions on pg_control and global, and
Postgres threw other errors but continued running.
4. I mv'd the files and that didn't trigger a shutdown.
5. I did a fast swap:
rm -rf /pgdata/*
cp -p -r /pgdata2/* /pgdata/
... as expected, this did NOT cause postgres to shut down.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2015-10-01 06:35:01 | Re: Parallel Seq Scan |
| Previous Message | oonishitk | 2015-10-01 04:01:00 | Re: max_worker_processes on the standby |