Re: First-draft release notes for next week's releases - Mailing list pgsql-hackers

From Greg Stark
Subject Re: First-draft release notes for next week's releases
Date
Msg-id CAM-w4HNqc==hsi-=-J_=tQV9fNTXPcDiXwoZV2YEiDb8HiKCRw@mail.gmail.com
Whole thread Raw
In response to Re: First-draft release notes for next week's releases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: First-draft release notes for next week's releases  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
On Mon, Mar 17, 2014 at 3:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm thinking we'd better promote that Assert to a normal runtime elog.


I wasn't sure about this but on further thought I think it's a really
good idea and should be mentioned in the release notes. One of the
things that's been bothering me about this bug is that it's really
hard to be know if your standby has suffered from the problem and if
you've promoted it you don't know if your database has a problem.

That said, it would be nice to actually fix the problem, not just
detect it. Eventually vacuum would fix the problem. I think. I'm not
really sure what will happen actually.

-- 
greg



pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Planner hints in Postgresql
Next
From: Robert Haas
Date:
Subject: Re: warning when compiling utils/tqual.h