Re: alpha5

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: alpha5
Date: 2011-03-28 13:25:32
Message-ID: AANLkTi=vte9W9k+7Ubpugz1MU7AV83a-fWqr=YGYePxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 26, 2011 at 9:41 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Per previous discussion, I'm going to wrap alpha5 Monday morning
> Eastern time, barring objections.

It seems that the 'make distcheck' build is broken. Apparently we
don't have any automated testing of this? Anyone know what to fix
here?

openjade:tempfile_HISTORY.sgml:674:55:X: reference to non-existent ID
"GUC-DEADLOCK-TIMEOUT"
openjade:tempfile_HISTORY.sgml:677:23:X: reference to non-existent ID
"GUC-LOG-MIN-DURATION-STATEMENT"
openjade:tempfile_HISTORY.sgml:678:23:X: reference to non-existent ID
"GUC-LOG-AUTOVACUUM-MIN-DURATION"
openjade:tempfile_HISTORY.sgml:1116:23:X: reference to non-existent ID
"SQL-ALTERTABLE"
openjade:tempfile_HISTORY.sgml:676:23:X: reference to non-existent ID
"GUC-MAX-STANDBY-STREAMING-DELAY"
openjade:tempfile_HISTORY.sgml:675:23:X: reference to non-existent ID
"GUC-MAX-STANDBY-ARCHIVE-DELAY"

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

  • alpha5 at 2011-03-27 01:41:42 from Robert Haas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-28 13:26:59 Re: alpha5
Previous Message Tom Lane 2011-03-28 13:21:43 Re: pgsql: Fix plpgsql to release SPI plans when a function or DO block is