Re: alpha3 release schedule?

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Hiroyuki Yamada <yamada(at)kokolink(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: alpha3 release schedule?
Date: 2009-12-19 17:12:22
Message-ID: 4B2D0976.6070709@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Hiroyuki Yamada <yamada(at)kokolink(dot)net> writes:
>> Well, I want to know whether the problem I refered to
>> in http://archives.postgresql.org/pgsql-hackers/2009-12/msg01641.php
>> is must-fix or not.
>
>> This problem is a corollary of the deadlock problem. This is less catstrophic
>> but more likely to happen.
>
>> If you leave this problem, for example, any long-running transactions,
>> holding any cursors in whatever tables, have a possibility of freezing
>> whole recovery work in HotStandby node until the transaction commit.
>
> Seems like something we should fix ASAP, but I do not see why it need
> hold up an alpha release. Alpha releases are expected to have bugs,
> and this one doesn't look like it would stop people from finding
> other bugs.

yeah afaik alpha tarballs are a forma of a checkpoint at the end of a
commitfest to get people a reasonable testing target. Every feature (not
only HS) deserves getting serious testing so I vote for getting alpha3
out as soon as possible.

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2009-12-19 17:24:41 Re: Backup history file should be replicated in Streaming Replication?
Previous Message Tom Lane 2009-12-19 16:54:02 Re: alpha3 release schedule?