| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "David Fetter" <david(at)fetter(dot)org>,"Florian Pflug" <fgp(at)phlo(dot)org>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: kill -KILL: What happens? |
| Date: | 2011-01-14 16:22:21 |
| Message-ID: | 4D3023DD0200002500039587@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> If postmaster dies, and then another backend crashes, then your
> backend running "your honking big query" could run across
> corrupted state and then you'd be in serious trouble.
Worst of all, it could give bogus results without error. I really
don't see a production use case for letting backends continue after
postmaster failure -- unless you only kinda, sorta care whether
committed data is actually retrievable or reported data is actually
accurate.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Kaltenbrunner | 2011-01-14 16:23:39 | Maintenance downtime for commitfest.postgresql.org and media.postgresql.org |
| Previous Message | Tatsuo Ishii | 2011-01-14 15:53:03 | Re: Error code for "terminating connection due to conflict with recovery" |