| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Benjamin Arai <me(at)benjaminarai(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: fsync=off & shutdown => crash? |
| Date: | 2008-02-09 23:03:27 |
| Message-ID: | 1733.1202598207@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Benjamin Arai <me(at)benjaminarai(dot)com> writes:
> I was reading the docuementation for 8.3
> (http://www.postgresql.org/docs/8.3/static/wal-async-commit.html) and it
> states "An immediate-mode shutdown is equivalent to a server crash, and
> will therefore cause loss of any unflushed asynchronous commits.". Does
> this mean that doing a "shutdown" (centos: /sbin/service postgresql
> stop) will be considered a crash?
Not unless the initscript uses an immediate-mode shutdown signal,
which would be a fairly unfriendly thing for it to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Arai | 2008-02-09 23:30:01 | Continual uptime while loading data ... COPY vs INSERTS within a transaction. |
| Previous Message | Benjamin Arai | 2008-02-09 22:52:40 | fsync=off & shutdown => crash? |