PostgreSQL 8.0 Feature List?

On Sun, 2004-08-08 at 22:37, CSN wrote:

Looking forward to PostgreSQL 8.0 :). Is there an
"official" feature list? What I've dug up so far:

nested transactions
transaction checkpoints
point in time recovery
tablespaces
native Windows port
plpgsql exceptions
integrated pg_autovacuum
ARC buffer code?

pg_autovacuum didn't quite make it, and will remain contrib. Maybe 8.1
or so.

Also add:

New background writer process.
The ability to set vacuum delay for heavily loaded databases.
Log rotation.

On 8 Aug 2004 at 21:37, CSN wrote:

native Windows port

I thought this one was coming with 7.5?

--Ray.

-------------------------------------------------------------
Raymond O'Donnell http://www.galwaycathedral.org/recitals
rod@iol.ie Galway Cathedral Recitals
-------------------------------------------------------------

Raymond O'Donnell wrote:

On 8 Aug 2004 at 21:37, CSN wrote:

native Windows port

I thought this one was coming with 7.5?

7.5 was renamed to 8.0

Regards
Gaetano Mendola

CSN wrote:

Looking forward to PostgreSQL 8.0 :). Is there an
"official" feature list? What I've dug up so far:

nested transactions
transaction checkpoints
point in time recovery
tablespaces
native Windows port
plpgsql exceptions
integrated pg_autovacuum
ARC buffer code?

Please look at the release notes as part of the docs on the developers
web site:

http://developer.postgresql.org

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Will PostgreSQL 8.0 include replication server (not contrib/*) and nested transactions support?

--
WBR, sector119

Am Dienstag, 10. August 2004 10:05 schrieb sector119@mail.ru:

Will PostgreSQL 8.0 include replication server (not contrib/*) and nested
transactions support?

No and yes.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On Tue, 2004-08-10 at 02:05, sector119@mail.ru wrote:

Will PostgreSQL 8.0 include replication server (not contrib/*) and nested transactions support?

What difference does it make if replication is contrib/* or an external
project or integrated? It's still the same thing. Plus, there are
currently no replication systems for postgresql that are all things to
all people, hence none are included or likely to be included.

Slony-I just came out in beta, and it appears to be quite a nice
replication system.

To put it bluntly, which would you rather have, a database with
integrated replication that had a flawed / unreliable replication
system, or a database with an external replication system that works
flawlessly? Integration is much less important than whether it
functions, and anyone who says otherwise has been drinking too much
marketing kool aid.

nested transactions / savepoints will be included.

Scott Marlowe wrote:

On Tue, 2004-08-10 at 02:05, sector119@mail.ru wrote:

Will PostgreSQL 8.0 include replication server (not contrib/*)
and nested transactions support?

Slony-I just came out in beta, and it appears to be quite a nice
replication system.

I wonder if it would be a good idea from a propaganda perspective to
include a reference to Slony-I in the press release and possibly the
release notes? Or would such an imprimatur be inappropriate?

Also, what is the etymology of the term Slony?

Mike Mascari

As to Slony:

in a few slavonic languages (I know about Czech, Slovak, Russian, maybe others
too, "slony" is the plural of "slon", e.g. elephant. Thus Slony = Elephants.

Cheers

Zoltan

Dňa Utorok 10. August 2004 11:51 ste napísali:

Am Dienstag, 10. August 2004 11:51 schrieb Mike Mascari:

I wonder if it would be a good idea from a propaganda perspective to
include a reference to Slony-I in the press release and possibly the
release notes? Or would such an imprimatur be inappropriate?

It will probably be in the press release, but not in the release notes.

Also, what is the etymology of the term Slony?

Russian:
slon = elephant
slony = elephants

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On Tue, 10 Aug 2004 03:17:00 -0600 Scott Marlowe <smarlowe@qwest.net> wrote:

Plus, there are
currently no replication systems for postgresql that are all things to
all people,

is this even possible?

(no, don't answer that, it's a rhetorical question.)

i can make a case that there are at least 3 distinctly different types
of replication needed depending on the application.

1) synchronous

2) single master, multiple slave asynchronous
(aka slony)

3) multi-master async w/conflict resolution
(like the now woefully out of date pg-replicator)

the work on slony is appreciated, but i need 3), and it
looks like i'm going to have to do it myself. sigh.

richard
--
Richard Welty rwelty@averillpark.net
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security

On 8/10/2004 5:51 AM, Mike Mascari wrote:

Scott Marlowe wrote:

On Tue, 2004-08-10 at 02:05, sector119@mail.ru wrote:

Will PostgreSQL 8.0 include replication server (not contrib/*)
and nested transactions support?

Slony-I just came out in beta, and it appears to be quite a nice
replication system.

Slony-I is released and we will follow up with a 1.0.2 that will support
PostgreSQL 8.0beta1 this week, so that people can test replicating their
7.x databases to 8.0 in preparation of upgrade switchover.

I wonder if it would be a good idea from a propaganda perspective to
include a reference to Slony-I in the press release and possibly the
release notes? Or would such an imprimatur be inappropriate?

The Slony team would appreciate this, but I think pointing to one
project only is inappropriate, given the current marketshare situation.
The marketshare should change quickly, because Slony-I is a highly
active project, as the instant 8.0 support demonstrates (CVS tip and
REL_1_0_STABLE branch run with 8.0beta1 so the 1.0.2 release is more or
less wrapping a tarball), while other replication projects are seriously
behind the release schedule. A fact that contradicts the ever so often
made claim that an integrated solution would have release schedule or
maintenance advantages. I cannot see the disadvantages of an external
project in this case.

However, replication is a top priority question and the press release
for 8.0 must address this. The more so because PostgreSQL seems to be
the only database that for good reasons does not come with a bundled or
builtin replication thingy, but rather relies on the diversity and
specialization of related projects.

Also, what is the etymology of the term Slony?

Elephants, especially this one: http://slony.info

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #

At 8/10/04 9:30 AM, JanWieck@Yahoo.com wrote:

Slony-I is released... [snip]

Also, what is the etymology of the term Slony?

Elephants, especially this one: http://slony.info

Is the project called "Slony-1" or "Slony1" (numeral one), or "Slony-I"
(uppercase i)?

It appears to be referred to multiple ways, even on the Web site, which
means that it's difficult to search for and I don't know how to pronounce
it when I talk to other people.

(I'm convinced that hard-to-pronounce names make people decide not to
mention cool things to other people for fear they'll look stupid,
directly resulting in less word-of-mouth.)

--
Robert L Mathews, Tiger Technologies http://www.tigertech.net/

"Ignorance more frequently begets confidence than does knowledge."
-- Darwin

On Tue, 2004-08-10 at 07:51, Richard Welty wrote:

On Tue, 10 Aug 2004 03:17:00 -0600 Scott Marlowe <smarlowe@qwest.net> wrote:

Plus, there are
currently no replication systems for postgresql that are all things to
all people,

is this even possible?

(no, don't answer that, it's a rhetorical question.)

i can make a case that there are at least 3 distinctly different types
of replication needed depending on the application.

1) synchronous

2) single master, multiple slave asynchronous
(aka slony)

3) multi-master async w/conflict resolution
(like the now woefully out of date pg-replicator)

the work on slony is appreciated, but i need 3), and it
looks like i'm going to have to do it myself. sigh.

On the upside, you have already been given pg-replicator as a starting
point, all you need to do is being it up to speed.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

On 11 Aug 2004 13:51:49 -0400 Robert Treat <xzilla@users.sourceforge.net> wrote:

On the upside, you have already been given pg-replicator as a starting
point, all you need to do is being it up to speed.

i have to rewrite it in a different language. it depends on tcl-dp, an unsupported
(and reportedly flakey) variant on tcl.

i'm quite experienced in C and Java, so it's going to be in one of those two.
any comments from anyone on the language choice?

sigh,
richard
--
Richard Welty rwelty@averillpark.net
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security

"RW" == Richard Welty <rwelty@averillpark.net> writes:

RW> i'm quite experienced in C and Java, so it's going to be in one of
RW> those two. any comments from anyone on the language choice?

eRServer is written in Java. It sucks up about 200Mb+ virtual memory
for a teeny-tiny little database. I'd avoid java :-)

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/

On Thu, 12 Aug 2004, Vivek Khera wrote:

"RW" == Richard Welty <rwelty@averillpark.net> writes:

RW> i'm quite experienced in C and Java, so it's going to be in one of
RW> those two. any comments from anyone on the language choice?

eRServer is written in Java. It sucks up about 200Mb+ virtual memory
for a teeny-tiny little database. I'd avoid java :-)

We felt the same way, that's why we've been working at re-writing it in
C++ ... new version is currently going into beta testing, so should
hopefully be available RSN ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

On Thu, 12 Aug 2004 14:36:13 -0400 Vivek Khera <khera@kcilink.com> wrote:

"RW" == Richard Welty <rwelty@averillpark.net> writes:

RW> i'm quite experienced in C and Java, so it's going to be in one of
RW> those two. any comments from anyone on the language choice?

eRServer is written in Java. It sucks up about 200Mb+ virtual memory
for a teeny-tiny little database. I'd avoid java :-)

java often sucks up too much memory. java doesn't have to suck
up too much memory, it just usually gets written that way.

richard
--
Richard Welty rwelty@averillpark.net
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security

Scott Marlowe wrote:

On Tue, 2004-08-10 at 02:05, sector119@mail.ru wrote:

Will PostgreSQL 8.0 include replication server (not contrib/*) and nested transactions support?

nested transactions / savepoints will be included.

what is a nested transaction?