Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: devrim(at)gunduz(dot)org
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Date: 2012-09-14 16:28:05
Message-ID: 15739.1347640085@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

"Devrim GUNDUZ" <devrim(at)gunduz(dot)org> writes:
> Does this mean we need to wrap new tarballs soon, because of the data loss
> bug?

I'll defer to Robert on whether this bug is serious enough to merit a
near-term release on its own. But historically, we've wanted to push
out a .1 update two or three weeks after a .0 release, to mop up
whatever new bugs are nasty enough for people to trip over right away.
Maybe we should be thinking in terms of a set of releases around the
end of September.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2012-09-14 17:17:27 Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Previous Message Tom Lane 2012-09-14 16:09:36 Re: pgsql: Back-patch fix and test case for bug #7516.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2012-09-14 17:17:27 Re: Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries.
Previous Message Rural Hunter 2012-09-14 15:53:38 Re: pg_upgrade from 9.1.3 to 9.2 failed