| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tracing down buildfarm "postmaster does not shut down" failures |
| Date: | 2016-02-10 03:08:41 |
| Message-ID: | 5180.1455073721@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> On 2/8/16 2:45 PM, Tom Lane wrote:
>> I had in mind to just "git revert" the patch when we're done with it.
> It's already difficult enough for DBAs to debug some performance issues,
> so getting rid of logging is a step backwards. I realize it's unlikely
> that you could run DEBUG2 in a prod environment, but we still shouldn't
> be reducing visibility.
Meh. It seems clear to me that we should move the "database system is
shut down" message so that it comes out only after the postmaster has
removed its lockfiles (and hence is really gone so far as any outside
vantage point is concerned). But I do not think any of the rest of
what I put in has any lasting value.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2016-02-10 03:09:03 | Re: Tracing down buildfarm "postmaster does not shut down" failures |
| Previous Message | Tom Lane | 2016-02-10 03:02:17 | Re: Tracing down buildfarm "postmaster does not shut down" failures |