The Hermit Hacker writes:
> if this is the case, can we look at applying that patch tonight, give ppl
> till Friday to test and put out a RC1 depending on the results?
This should probably be called beta6, given that there is a lot of new
code in it.
--
Peter Eisentraut [EMAIL PROTECTED]
On Mon, 12 Mar 2001, Tom Lane wrote:
> >> if this is the case, can we look at applying that patch
> >> tonight, give ppl till Friday to test and put out a RC1
> >> depending on the results?
>
> Patch committed. There are still some loose ends to clean up:
>
> * I need to finish making an xlog-re
>> if this is the case, can we look at applying that patch
>> tonight, give ppl till Friday to test and put out a RC1
>> depending on the results?
Patch committed. There are still some loose ends to clean up:
* I need to finish making an xlog-reset utility for contrib.
* I stubbed out shmctl(
> > but it's hard to notice eg misprints in 44K file -:)
> > I think we should apply patches and hard test
> > recovering for a few days (power off/pg_ctl -m i stop
> > with dozens update transactions).
>
> if this is the case, can we look at applying that patch
> tonight, give ppl till Friday t
On Mon, 12 Mar 2001, Mikheev, Vadim wrote:
> but it's hard to notice eg misprints in 44K file -:)
> I think we should apply patches and hard test
> recovering for a few days (power off/pg_ctl -m i stop
> with dozens update transactions).
if this is the case, can we look at applying that patch to
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> but it's hard to notice eg misprints in 44K file -:)
> I think we should apply patches and hard test
> recovering for a few days (power off/pg_ctl -m i stop
> with dozens update transactions).
OK. I haven't finished putting together an xlog-reset ut
