Re: [Fwd: Re: [CORE] Going Beta on Monday ...]

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
Cc: Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Fwd: Re: [CORE] Going Beta on Monday ...]
Date: 2000-12-10 21:57:44
Message-ID: 200012102157.QAA05870@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I will work on a list this week. It will have the same format as usual,
if that is OK.

> > I browsed through the CVS logs and made this list of the important
> > stuff. There's a ton of less important stuff...
>
> Shall we consider this the start of the list then? I think there may be
> a couple of things already mentioned in the release note stubs for 7.1
> too.
>
> - Thomas
>
> Additional items:
>
> AT TIME ZONE clause for date/time types
> OVERLAPS operator support rewritten
>
> WAL --- fsync reliability without the performance hit
> TOAST --- 8K row limit is no longer significant
> outer joins (per SQL92 syntax, not Oracle's)
> subselects in FROM clause
> views and subselects now allow union/intersect/except, order by, limit
> views containing grouping, aggregates, DISTINCT work now
> bit-string types work now
> function manager overhaul: fixes portability problems, NULL-argument
> handling
> memory management overhaul: prevent memory leak accumulation during
> queries
> drop table and rename table are now rollback-able (transaction-safe)
> extensive overhaul of configure/build mechanism
> overhaul of parameter-setting mechanisms (postmaster flags,
> postmaster.opts,
> etc)
> more efficient large-object implementation
> pg_dump can dump large objects now
> pg_dump does the right thing with user-added objects in template1
> support for binding postmaster's IP socket to a virtual host name
> support for placing postmaster's Unix socket file elsewhere than /tmp
> keep reference counts on syscache entries to avoid dropping still-used
> entries
> Protect against changes in LOCALE environment causing corrupted indexes
> better handling of unknown-type literals (default to string type more
> readily)
> inet/cidr datatypes cleaned up
> LIKE/ESCAPE implemented, also ILIKE (case-insensitive LIKE)
> aggregate-function support redesigned: only one transition function now,
> cleaner handling of NULLs
> STDDEV() and VARIANCE() aggregates added
> SUM() and AVG() on integer datatypes use NUMERIC accumulators
> Child tables are now scanned by default -- ie, if foo has children then
> SELECT FROM foo means SELECT FROM foo*. Ditto for UPDATE and DELETE.
> Use SELECT FROM ONLY foo if you don't want this behavior.
> vacuum analyze does the analyze part without holding exclusive lock
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2000-12-10 22:02:35 Re: [HACKERS] Bug in index scans with Locale support enabled
Previous Message Bruce Guenter 2000-12-10 21:38:29 Re: Re: CRC