On Tue, 3 Sep 2002, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Yes, I haven't gotten to the release checklist yet. Let's delay a day.
>
> Or at least late in the day tomorrow. I have some loose ends to clean
> up yet as well, but I'm beat and am going to bed.
>
> But I assu
S'alright, I can do the package together tomorrow morning to let you wrap
up the loose ends :)
On Tue, 3 Sep 2002, Bruce Momjian wrote:
> I am still working on the 7.3 HISTORY file. I have extracted the items,
> but I have to worksmith them and write an introduction.
>
> It is midnight here no
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Yes, I haven't gotten to the release checklist yet. Let's delay a day.
Or at least late in the day tomorrow. I have some loose ends to clean
up yet as well, but I'm beat and am going to bed.
But I assume we are now officially in feature freeze, right
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I don't know of any other items holding up the packaging.
>
> Gotta brand the thing as 7.3beta1 not 7.3devel, no?
Yes, I haven't gotten to the release checklist yet. Let's delay a day.
I have a 17k line log file down to 3.5k lines
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I don't know of any other items holding up the packaging.
Gotta brand the thing as 7.3beta1 not 7.3devel, no?
regards, tom lane
---(end of broadcast)---
TIP 5: Have you checked ou
I am still working on the 7.3 HISTORY file. I have extracted the items,
but I have to worksmith them and write an introduction.
It is midnight here now. I don't think I can finish before ~3am and at
that point, I am not sure I will know what I am writing.
Basically, one day of feature freeze w
> | Fix for inherited CHECK constraints (Stephan Szabo)
>
> ditto
If this is what I think it is, I think the actual fix was the
following (although I don't know what a particularly good wording
is)
ALTER TABLE ADD CONSTRAINT now properly adds check constraints
to children of the specified tab
I find the HISTORY file to be distressingly poor to peruse. Reasons:
A large proportion of the items don't convey any useful information.
Examples:
| PLpgSQL fix for SELECT... FOR UPDATE (Tom)
What did this fix? Does SELECT FOR UDPATE now work whereas it didn't use
to? => "SELECT ... FOR UPDA
>
> May be it's cosmetic, but:
>
> - "Migration to 7.1" right is "Migration to 7.2"
Fixed.
>
> Be missing:
>
> - information that some parts of interface are translated to
>Swedish, Russian, French, Germany nad Czech.
> (IMHO right place for information about Peter's NLS suppo
May be it's cosmetic, but:
- "Migration to 7.1" right is "Migration to 7.2"
Be missing:
- information that some parts of interface are translated to
Swedish, Russian, French, Germany nad Czech.
(IMHO right place for information about Peter's NLS support is
"Major changes in th
10 matches
Mail list logo
