Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-26 Thread Markus Schaber
Hi, Bruce,

Bruce Momjian wrote:

   listitem
para
 Allow inheritance to be removed from tables
/para
   /listitem

I'd enhance that to Allow table inheritance relationships to be defined
for and removed from pre-existing tables.

HTH,
Markus

-- 
Markus Schaber | Logical TrackingTracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org



signature.asc
Description: OpenPGP digital signature


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-26 Thread Bruce Momjian
Markus Schaber wrote:
-- Start of PGP signed section.
 Hi, Bruce,
 
 Bruce Momjian wrote:
 
listitem
 para
  Allow inheritance to be removed from tables
 /para
/listitem
 
 I'd enhance that to Allow table inheritance relationships to be defined
 for and removed from pre-existing tables.

Good point.  Updated wording:

Allow table inheritance to be added and removed from
pre-existing tables   

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-26 Thread Markus Schaber
Hi, Bruce,

Bruce Momjian wrote:
 Allow inheritance to be removed from tables
 I'd enhance that to Allow table inheritance relationships to be defined
 for and removed from pre-existing tables.
 
 Good point.  Updated wording:
 
 Allow table inheritance to be added and removed from
   pre-existing tables   

Agree, that's excellent.


Thanks,
Markus
-- 
Markus Schaber | Logical TrackingTracing International AG
Dipl. Inf. | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org



signature.asc
Description: OpenPGP digital signature


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-26 Thread Bruce Momjian
Andrew Dunstan wrote:
 Bruce Momjian wrote:
  I created a major features list for 8.2 and put it into CVS.  Instead of
  going into detail (meaning the item would not appear in the Changes
  section below, I just highlighted some of the big stuff, and was
  purposely vague about the details, so people just have an overview of
  what is below.
 
  Let me know how it looks.

 
 
 Some of these just look rather vague. For example:
 
 *
 
   More control over creating/dropping objects and inheritance
 
 
 If I did not know what the features were, that item would convey nothing 
 to me. The fact that you can add/drop the inheritance characteristics of 
 a table after its creation isn't something I would just lump under more 
 control - it's a major new feature that will possibly revolutionize the 
 way people use inheritance, especially for partitioning.

OK, split items up:

  listitem
   para
More control over creating and dropping objects
   /para
  /listitem

  listitem
   para
Allow inheritance to be removed from tables
   /para
  /listitem

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread Jim C. Nasby
On Fri, Sep 22, 2006 at 12:59:36PM -0700, Joe Conway wrote:
 Andrew Sullivan wrote:
 On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:
 
 Regardless, I think we should include a section of major new
 projects/developments from pgFoundry, because they ultimately make
 PostgreSQL a more useful database. Maybe this list should only be in the
 
 I like that.  New enhancement products or something?
 
enhancement products makes me think if Encyte and the like... :P Maybe
add-ons would be better?

 In that case, what about things on gborg too? I just updated PL/R for 
 8.2 compatibility (and finally changed the status from alpha to beta).
 
 BTW, I'm happy to move PL/R over to pgFoundry, but became a little 
 concerned about doing that after seeing the lengthy thread regarding 
 pgFoundry concerns (but admittedly, I didn't have time to read the 
 thread in detail, because I'm back over in Germany on a long business 
 trip again).

I didn't mention gforge since it'd depricated, but I don't see an issue
with listing any add-on projects, no matter where they're hosted. For
example, didn't pgAdmin just add support for Slony? That's something
worth mentioning.
-- 
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB  http://enterprisedb.com  512.569.9461 (cell)

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread Dave Page
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
 Sent: 25 September 2006 15:03
 To: Joe Conway
 Cc: Andrew Sullivan; pgsql-hackers@postgresql.org
 Subject: Re: [HACKERS] Release Notes: Major Changes in 8.2
 
 For
 example, didn't pgAdmin just add support for Slony? That's something
 worth mentioning.

That was our last major release. You can see what will be in 1.6 at
http://www.pgadmin.org/development/changelog.php

Regards, Dave

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread David Fetter
On Mon, Sep 25, 2006 at 03:10:39PM +0100, Dave Page wrote:
  From: [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Jim C. Nasby
  
  For example, didn't pgAdmin just add support for Slony? That's
  something worth mentioning.
 
 That was our last major release. You can see what will be in 1.6 at
 http://www.pgadmin.org/development/changelog.php

Could you clarify this a bit?  As far as I can tell, it's not possible
to set up slony initially with pgadmin 1.4.latest.  Has this changed
in 1.6?

Cheers,
D

-- 
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 415 235 3778AIM: dfetter666
  Skype: davidfetter

Remember to vote!

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread Dave Page
 

 -Original Message-
 From: David Fetter [mailto:[EMAIL PROTECTED] 
 Sent: 25 September 2006 16:57
 To: Dave Page
 Cc: Jim C. Nasby; Joe Conway; Andrew Sullivan; 
 pgsql-hackers@postgresql.org
 Subject: Re: [HACKERS] Release Notes: Major Changes in 8.2
 
 On Mon, Sep 25, 2006 at 03:10:39PM +0100, Dave Page wrote:
   From: [EMAIL PROTECTED] 
   [mailto:[EMAIL PROTECTED] On Behalf Of 
 Jim C. Nasby
   
   For example, didn't pgAdmin just add support for Slony? That's
   something worth mentioning.
  
  That was our last major release. You can see what will be in 1.6 at
  http://www.pgadmin.org/development/changelog.php
 
 Could you clarify this a bit?  As far as I can tell, it's not possible
 to set up slony initially with pgadmin 1.4.latest.  Has this changed
 in 1.6?

The only change to the Slony support in 1.6 is a minor update to allow
it to initialise a Slony 1.2 cluster (the version number needs to be
inserted into the slony1_funcs script now). 

The only parts of the initial setup that pgAdmin doesn't do are the
installation of the Slony shared libraries, or the copying of the schema
(actually, pgAdmin can do this - it just doesn't do it automagically.
Just backup and restore the relevant bits of your schema on the slave
nodes).

All the Slony support in pgAdmin was written as part of a contract with
a Japanese company (SKC) to port Slony to Windows - that work was
finished almost a year ago.

Regards, Dave


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread Josh Berkus

Folks,


On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:

Regardless, I think we should include a section of major new
projects/developments from pgFoundry, because they ultimately make
PostgreSQL a more useful database. Maybe this list should only be in the


I like that.  New enhancement products or something?

A



If you're following the release drafting in pgsql-advocacy, you'll see 
that we're planning on including a section about pgfoundry projects in 
the extended release on the web, or press kit.  So far, I've listed 
pgPool, PL/Java and Full Disjunctions; I'm not sure what else to list. 
Suggestions welcome.


--Josh Berkus

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-25 Thread Andrew Sullivan
On Fri, Sep 22, 2006 at 12:59:36PM -0700, Joe Conway wrote:
 
 In that case, what about things on gborg too?

Yes, same idea.  I don't care where the project _lives_; the
important thing is its integration with PostgreSQL (and its quality).

A

-- 
Andrew Sullivan  | [EMAIL PROTECTED]
When my information changes, I alter my conclusions.  What do you do sir?
--attr. John Maynard Keynes

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-22 Thread Simon Riggs
On Thu, 2006-09-21 at 21:45 -0400, Bruce Momjian wrote:

 Let me know how it looks.

Very Good



Very last, Minor change thoughts:

  * Continuous archiving enhancements 

change: Warm Standby enhancements

The improvements to Continuous Archiving relate directly to the
creation of Warm Standby servers, so it would be better to
mention Warm Standby, not Continuous Archiving (and definitely
not PITR)

  * Monitoring and logging additions 

add to end of line: improve performance tuning capability

  * COPY support for SELECT statements 

change: COPY TO support ...

add to end of line: enhances data unload

  * Array and aggregate improvements 

add  to end of line: , plus SQL:2003 statistical functions

-- 
  Simon Riggs 
  EnterpriseDB   http://www.enterprisedb.com


---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-22 Thread Bruce Momjian

Great, all added.

---

Simon Riggs wrote:
 On Thu, 2006-09-21 at 21:45 -0400, Bruce Momjian wrote:
 
  Let me know how it looks.
 
 Very Good
 
 
 
 Very last, Minor change thoughts:
 
   * Continuous archiving enhancements 
 
 change: Warm Standby enhancements
 
 The improvements to Continuous Archiving relate directly to the
 creation of Warm Standby servers, so it would be better to
 mention Warm Standby, not Continuous Archiving (and definitely
 not PITR)
 
   * Monitoring and logging additions 
 
 add to end of line: improve performance tuning capability
 
   * COPY support for SELECT statements 
 
 change: COPY TO support ...
 
 add to end of line: enhances data unload
 
   * Array and aggregate improvements 
 
 add  to end of line: , plus SQL:2003 statistical functions
 
 -- 
   Simon Riggs 
   EnterpriseDB   http://www.enterprisedb.com
 
 
 ---(end of broadcast)---
 TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-22 Thread Andrew Sullivan
On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:
 Regardless, I think we should include a section of major new
 projects/developments from pgFoundry, because they ultimately make
 PostgreSQL a more useful database. Maybe this list should only be in the

I like that.  New enhancement products or something?

A

-- 
Andrew Sullivan  | [EMAIL PROTECTED]
I remember when computers were frustrating because they *did* exactly what 
you told them to.  That actually seems sort of quaint now.
--J.D. Baldwin

---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-22 Thread Andrew Dunstan

Bruce Momjian wrote:

I created a major features list for 8.2 and put it into CVS.  Instead of
going into detail (meaning the item would not appear in the Changes
section below, I just highlighted some of the big stuff, and was
purposely vague about the details, so people just have an overview of
what is below.

Let me know how it looks.
  



Some of these just look rather vague. For example:

   *

 More control over creating/dropping objects and inheritance


If I did not know what the features were, that item would convey nothing 
to me. The fact that you can add/drop the inheritance characteristics of 
a table after its creation isn't something I would just lump under more 
control - it's a major new feature that will possibly revolutionize the 
way people use inheritance, especially for partitioning.


cheers

andrew




---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-22 Thread Joe Conway

Andrew Sullivan wrote:

On Thu, Sep 21, 2006 at 03:05:36PM -0500, Jim C. Nasby wrote:


Regardless, I think we should include a section of major new
projects/developments from pgFoundry, because they ultimately make
PostgreSQL a more useful database. Maybe this list should only be in the


I like that.  New enhancement products or something?


In that case, what about things on gborg too? I just updated PL/R for 
8.2 compatibility (and finally changed the status from alpha to beta).


BTW, I'm happy to move PL/R over to pgFoundry, but became a little 
concerned about doing that after seeing the lengthy thread regarding 
pgFoundry concerns (but admittedly, I didn't have time to read the 
thread in detail, because I'm back over in Germany on a long business 
trip again).


Joe


---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Zdenek Kotala

Simon Riggs napsal(a):



Improved monitoring and performance tuning (Tom, Bruce, Greg, Larry)

Overhead of statistics collection has been considerably reduced and new
statistics and system information is available. Better query logging
improves diagnostics and especially performance tuning. Server now
includes DTrace support. Indexes can now also be created CONCURRENTLY,
allowing application tuning without effecting server availability.



You forgot to Robert Lor - author of DTrace support.

Zdenek

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Simon Riggs
On Wed, 2006-09-20 at 23:22 -0400, Bruce Momjian wrote:

 Usually the major items just jump out of the release list.  In this
 case, nothing really jumped out, and I felt if I listed sereral, it was
 going to look weak because they were not big things, so I figured I
 would just go with the broad list.

Look back at the 7.4 release notes as a comparison. I think 8.0 was such
a milestone release we tend to judge ourselves by that and maybe feel
like the pace has slackened. IMHO, it has accelerated. We hit the lower
hanging fruit first, so early features were major items; later items
seem smaller and less important by comparison, especially when completed
by a team rather than a few individuals.

I don't think it matters whether the new features originated as a single
patch or as a stream of smaller patches. The end result is a major
improvement in a specific area. Picking one area I'm more familiar with,
sort performance was increased over many patches by many people, but the
original objective of making a step-change in that area *has* been
achieved (even if there are some additional gains still to be had for
certain narrower use-cases).

The role of the Major changes section is to provide a summary for
administrators who need to understand what a new release will give them
and make a cost/benefit judgement. We want people to understand the good
work that has been done and that does involve some filtering and
summarization, and its possibly true that it is harder in this release
than others. 

We need a Major changes section: People don't read the detail: sysadmins
are too busy these days. If there are no major features listed, people
will assume there are none and say oh its just a bug fix release. If
we aren't encouraging people to upgrade, why release at all? Maybe
people only upgrade every other release - if so, we'll get all of the
8.0 upgraders.

Improving scalability in 8.1 was great. Improving it again in 8.2 is
amazing and we should tell people, even if it sounds somewhat boring
because we did it last time as well. I think: again, wow, this software
is going places. Personally, I'll be ecstatic if we can do that again
for 8.3...

 Or perhaps we can do more broad-stroke list items, like monitoring or
 performance, as listed below.

Whether we like my list or not, I think such a grouped list should
exist. I'm mainly seeking to persuade you on that point and would be
comfortable even if you came up with a different grouped list.

Seeing a list of names after a topic emphasises the community
development process. In some cases, there was a stated objective and
that has been achieved. In other cases there was a community-driven move
in directions maybe we didn't predict. In the latter case, surely it is
the strength of open source that evolution works so well and really does
produce noticeably major changes. The changes in monitoring and tuning
tools is an excellent example: many smaller changes making a significant
improvement.

Please vote in favour of a Major Changes section.

-- 
  Simon Riggs 
  EnterpriseDB   http://www.enterprisedb.com


---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Bruce Momjian
Josh Berkus wrote:
 Bruce,
 
 What happened to PL/pgSQL debugging?  Did it die?

The debuggers is going to be on pgfoundry, if it isn't there already. 
The idea is that it would be loadable for 8.2, work out all the bugs,
and perhaps included in 8.3.

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Bruce Momjian

OK, I will work it.

---

Simon Riggs wrote:
 On Wed, 2006-09-20 at 23:22 -0400, Bruce Momjian wrote:
 
  Usually the major items just jump out of the release list.  In this
  case, nothing really jumped out, and I felt if I listed sereral, it was
  going to look weak because they were not big things, so I figured I
  would just go with the broad list.
 
 Look back at the 7.4 release notes as a comparison. I think 8.0 was such
 a milestone release we tend to judge ourselves by that and maybe feel
 like the pace has slackened. IMHO, it has accelerated. We hit the lower
 hanging fruit first, so early features were major items; later items
 seem smaller and less important by comparison, especially when completed
 by a team rather than a few individuals.
 
 I don't think it matters whether the new features originated as a single
 patch or as a stream of smaller patches. The end result is a major
 improvement in a specific area. Picking one area I'm more familiar with,
 sort performance was increased over many patches by many people, but the
 original objective of making a step-change in that area *has* been
 achieved (even if there are some additional gains still to be had for
 certain narrower use-cases).
 
 The role of the Major changes section is to provide a summary for
 administrators who need to understand what a new release will give them
 and make a cost/benefit judgement. We want people to understand the good
 work that has been done and that does involve some filtering and
 summarization, and its possibly true that it is harder in this release
 than others. 
 
 We need a Major changes section: People don't read the detail: sysadmins
 are too busy these days. If there are no major features listed, people
 will assume there are none and say oh its just a bug fix release. If
 we aren't encouraging people to upgrade, why release at all? Maybe
 people only upgrade every other release - if so, we'll get all of the
 8.0 upgraders.
 
 Improving scalability in 8.1 was great. Improving it again in 8.2 is
 amazing and we should tell people, even if it sounds somewhat boring
 because we did it last time as well. I think: again, wow, this software
 is going places. Personally, I'll be ecstatic if we can do that again
 for 8.3...
 
  Or perhaps we can do more broad-stroke list items, like monitoring or
  performance, as listed below.
 
 Whether we like my list or not, I think such a grouped list should
 exist. I'm mainly seeking to persuade you on that point and would be
 comfortable even if you came up with a different grouped list.
 
 Seeing a list of names after a topic emphasises the community
 development process. In some cases, there was a stated objective and
 that has been achieved. In other cases there was a community-driven move
 in directions maybe we didn't predict. In the latter case, surely it is
 the strength of open source that evolution works so well and really does
 produce noticeably major changes. The changes in monitoring and tuning
 tools is an excellent example: many smaller changes making a significant
 improvement.
 
 Please vote in favour of a Major Changes section.
 
 -- 
   Simon Riggs 
   EnterpriseDB   http://www.enterprisedb.com
 
 
 ---(end of broadcast)---
 TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Dave Page
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
 Sent: 21 September 2006 16:25
 To: Josh Berkus
 Cc: pgsql-hackers@postgresql.org; Simon Riggs
 Subject: Re: [HACKERS] Release Notes: Major Changes in 8.2
 
 Josh Berkus wrote:
  Bruce,
  
  What happened to PL/pgSQL debugging?  Did it die?
 
 The debuggers is going to be on pgfoundry, if it isn't there already. 
 The idea is that it would be loadable for 8.2, work out all the bugs,
 and perhaps included in 8.3.

We've also discussed bundling the GUI with pgAdmin for 1.8 (which will
be released with 8.3) so that idea could work out nicely.

Regards, Dave.

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Josh Berkus

Bruce, All:

The debuggers is going to be on pgfoundry, if it isn't there already. 
The idea is that it would be loadable for 8.2, work out all the bugs,

and perhaps included in 8.3.



So, should I take this off the press list for 8.2 and save it for 8.3, 
when the feature will be actually useful?


Second question:  are the Advisory Locks actually a unique PostgreSQL 
feature, or are these something other databases already have?


--Josh Berkus


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Jim C. Nasby
On Thu, Sep 21, 2006 at 11:24:53AM -0400, Bruce Momjian wrote:
 Josh Berkus wrote:
  Bruce,
  
  What happened to PL/pgSQL debugging?  Did it die?
 
 The debuggers is going to be on pgfoundry, if it isn't there already. 
 The idea is that it would be loadable for 8.2, work out all the bugs,
 and perhaps included in 8.3.

But didn't we end up putting some hooks in the backend to make this
possible?

Regardless, I think we should include a section of major new
projects/developments from pgFoundry, because they ultimately make
PostgreSQL a more useful database. Maybe this list should only be in the
PR (and not the release notes)...
-- 
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB  http://enterprisedb.com  512.569.9461 (cell)

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Bruce Momjian
Josh Berkus wrote:
 Bruce, All:
 
  The debuggers is going to be on pgfoundry, if it isn't there already. 
  The idea is that it would be loadable for 8.2, work out all the bugs,
  and perhaps included in 8.3.
  
 
 So, should I take this off the press list for 8.2 and save it for 8.3, 
 when the feature will be actually useful?

Yes, I think so.

 Second question:  are the Advisory Locks actually a unique PostgreSQL 
 feature, or are these something other databases already have?

Probably not unique.

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Chris Browne
[EMAIL PROTECTED] (Bruce Momjian) writes:
 Josh Berkus wrote:
 Bruce,
 
 What happened to PL/pgSQL debugging?  Did it die?

 The debuggers is going to be on pgfoundry, if it isn't there already. 
 The idea is that it would be loadable for 8.2, work out all the bugs,
 and perhaps included in 8.3.

If we now have the hooks in place, then it is surely worth saying so.
To then point people to pgFoundry for an add-on debugger application
seems pretty fair.
-- 
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://linuxdatabases.info/info/finances.html
Rules of the Evil Overlord #133.  If I find my beautiful consort with
access to  my fortress has been  associating with the  hero, I'll have
her executed.  It's regrettable,  but new consorts  are easier  to get
than new fortresses  and maybe the next one will  pay attention at the
orientation meeting. http://www.eviloverlord.com/

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Karen Hill
Simon Riggs wrote:


 SQL:2003 Analytical functions (Sergey, Tom, Neil)

   All statistical aggregate functions defined by SQL:2003 are now
 supported and user-defined aggregates now can take multiple columns as
 inputs.


Could this be a good starting point for SQL:2003 Window functions as
now the work on SQL:2003 statistical functions are done?  As
experienced postgres developers what would be your roadmap to implement
window functions?


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-21 Thread Bruce Momjian

I created a major features list for 8.2 and put it into CVS.  Instead of
going into detail (meaning the item would not appear in the Changes
section below, I just highlighted some of the big stuff, and was
purposely vague about the details, so people just have an overview of
what is below.

Let me know how it looks.

Simon's list below looks good, but it really has a lot of details,
particuarly it goes into use-cases for many of the features, and in fact
goes into more detail that we even have in the release notes now.  Is
that what people want?  My concern is that if we push too much
information, it is hard to see the actual features, i.e. if we say, we
have feature X, and it is good for Y, Z, and Q do people remember Y and
Z and forget X?

Again, I don't want to be the person writing these release notes, so I
am looking for feedback, good or bad.

---

Simon Riggs wrote:
 I'd like to include a section on Major changes in this release at the
 top of the release notes, as has been done for at least the last 6 major
 releases. The notes below are one stab at that, for **discussion**. I've
 tried to arrange specific changes into groups... 
 
 
 Major changes in this release:
 
 Improved scalability and performance on multi-processor systems (Tom,
 Alvaro, Itagaki, Qingqing, Heikki)
 
   A variety of changes improves the performance of both sequential scans
 and index scans, as well as enhancing multi-processor scalability. The
 advanced query optimizer has also been further enhanced, allowing
 indexes and partitioning to be useful in more cases. 
 
 Improved utility and large query performance (Tom, Simon, Alon, Andreas)
 
   Large sorts will have typical performance increases of 100-300%,
 improving complex queries and creating new indexes. Loading times have
 also been reduced. Large queries, data loads, upgrades and restores will
 be considerably improved.
 
 Improved monitoring and performance tuning (Tom, Bruce, Greg, Larry)
 
   Overhead of statistics collection has been considerably reduced and new
 statistics and system information is available. Better query logging
 improves diagnostics and especially performance tuning. Server now
 includes DTrace support. Indexes can now also be created CONCURRENTLY,
 allowing application tuning without effecting server availability.
 
 Zero administration overhead now possible (Alvaro)
 
   With autovacuum enabled, all required vacuuming will now take place
 without administrator intervention enabling wider distribution of
 embedded databases.
 
 Improved defaults and configuration (Peter, Andrew)
 
   Installation defaults are now improved for many tunable memory
 parameters and these can now be specified in kB, MB and GB. 
 
 Warm Standby Servers for High Availability (Simon, Tom)
 
   Warm Standby servers can now be more easily configured and are
 appropriate in a wider range of circumstances than previously.
 
 Improved scalability and performance of text search: GIN and Tsearch2
 (Teodor, Oleg)
 
   New GIN indexes allow much larger text search indexes than were
 previously possible. TSearch2 has been enhanced and performance has also
 been greatly improved.
 
 Enhanced DML Functionality (Jonah, Joe, Tom, Susanne, Atsushi)
 
   INSERT/UPDATE/DELETE RETURNING and INSERT .. VALUES (), VALUES (),
 VALUES () allow more efficient application designs. Enhancements to
 UPDATE and DELETE allow additional constructs for clarity and ease of
 use.
 
 SQL:2003 Analytical functions (Sergey, Tom, Neil)
 
   All statistical aggregate functions defined by SQL:2003 are now
 supported and user-defined aggregates now can take multiple columns as
 inputs.
 
 -- 
   Simon Riggs 
   EnterpriseDB   http://www.enterprisedb.com
 
 
 ---(end of broadcast)---
 TIP 4: Have you searched our list archives?
 
http://archives.postgresql.org

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Andreas Pflug
Simon Riggs wrote:
 Zero administration overhead now possible (Alvaro)

   With autovacuum enabled, all required vacuuming will now take place
 without administrator intervention enabling wider distribution of
 embedded databases.
   
This was true for 8.1 already, no?

Regards,
Andreas


---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Joshua D. Drake

Andreas Pflug wrote:

Simon Riggs wrote:

Zero administration overhead now possible (Alvaro)

With autovacuum enabled, all required vacuuming will now take place
without administrator intervention enabling wider distribution of
embedded databases.
  

This was true for 8.1 already, no?


No. 8.1 did not have it turned on by default.

Sincerely,

Joshua D. Drake




Regards,
Andreas


---(end of broadcast)---
TIP 6: explain analyze is your friend




--

   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
   Providing the most comprehensive  PostgreSQL solutions since 1997
 http://www.commandprompt.com/



---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

  http://www.postgresql.org/docs/faq


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Simon Riggs
On Wed, 2006-09-20 at 18:22 +0200, Andreas Pflug wrote:
 Simon Riggs wrote:
  Zero administration overhead now possible (Alvaro)
 
  With autovacuum enabled, all required vacuuming will now take place
  without administrator intervention enabling wider distribution of
  embedded databases.

 This was true for 8.1 already, no?

Hmmm. You're correct.

Perhaps that is not a major change after all.

-- 
  Simon Riggs 
  EnterpriseDB   http://www.enterprisedb.com


---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Gregory Stark

Joshua D. Drake [EMAIL PROTECTED] writes:

 No. 8.1 did not have it turned on by default.

Neither does 8.2 though.

-- 
  Gregory Stark
  EnterpriseDB  http://www.enterprisedb.com

---(end of broadcast)---
TIP 6: explain analyze is your friend


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Alvaro Herrera
Simon Riggs wrote:
 On Wed, 2006-09-20 at 18:22 +0200, Andreas Pflug wrote:
  Simon Riggs wrote:
   Zero administration overhead now possible (Alvaro)
  
 With autovacuum enabled, all required vacuuming will now take place
   without administrator intervention enabling wider distribution of
   embedded databases.
 
  This was true for 8.1 already, no?
 
 Hmmm. You're correct.
 
 Perhaps that is not a major change after all.

What happened in 8.2 is that you no longer need database-wide vacuums,
ever (except for template databases).  Not sure if that qualifies as a
major change or not.

-- 
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Joshua D. Drake

Gregory Stark wrote:

Joshua D. Drake [EMAIL PROTECTED] writes:


No. 8.1 did not have it turned on by default.


Neither does 8.2 though.


oh... heh.

J







--

   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
   Providing the most comprehensive  PostgreSQL solutions since 1997
 http://www.commandprompt.com/



---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Bruce Momjian

Usually the major items just jump out of the release list.  In this
case, nothing really jumped out, and I felt if I listed sereral, it was
going to look weak because they were not big things, so I figured I
would just go with the broad list.

The criteria I usually use are things that were not easy to do before.

Does the list below look good for inclusion?

I guess my point is that what we have now overwhelms people with the
number of small things we did.  If you try to put a few at the top, does
it diminish it because the top things are not large?

Or perhaps we can do more broad-stroke list items, like monitoring or
performance, as listed below.

---

Simon Riggs wrote:
 I'd like to include a section on Major changes in this release at the
 top of the release notes, as has been done for at least the last 6 major
 releases. The notes below are one stab at that, for **discussion**. I've
 tried to arrange specific changes into groups... 
 
 
 Major changes in this release:
 
 Improved scalability and performance on multi-processor systems (Tom,
 Alvaro, Itagaki, Qingqing, Heikki)
 
   A variety of changes improves the performance of both sequential scans
 and index scans, as well as enhancing multi-processor scalability. The
 advanced query optimizer has also been further enhanced, allowing
 indexes and partitioning to be useful in more cases. 
 
 Improved utility and large query performance (Tom, Simon, Alon, Andreas)
 
   Large sorts will have typical performance increases of 100-300%,
 improving complex queries and creating new indexes. Loading times have
 also been reduced. Large queries, data loads, upgrades and restores will
 be considerably improved.
 
 Improved monitoring and performance tuning (Tom, Bruce, Greg, Larry)
 
   Overhead of statistics collection has been considerably reduced and new
 statistics and system information is available. Better query logging
 improves diagnostics and especially performance tuning. Server now
 includes DTrace support. Indexes can now also be created CONCURRENTLY,
 allowing application tuning without effecting server availability.
 
 Zero administration overhead now possible (Alvaro)
 
   With autovacuum enabled, all required vacuuming will now take place
 without administrator intervention enabling wider distribution of
 embedded databases.
 
 Improved defaults and configuration (Peter, Andrew)
 
   Installation defaults are now improved for many tunable memory
 parameters and these can now be specified in kB, MB and GB. 
 
 Warm Standby Servers for High Availability (Simon, Tom)
 
   Warm Standby servers can now be more easily configured and are
 appropriate in a wider range of circumstances than previously.
 
 Improved scalability and performance of text search: GIN and Tsearch2
 (Teodor, Oleg)
 
   New GIN indexes allow much larger text search indexes than were
 previously possible. TSearch2 has been enhanced and performance has also
 been greatly improved.
 
 Enhanced DML Functionality (Jonah, Joe, Tom, Susanne, Atsushi)
 
   INSERT/UPDATE/DELETE RETURNING and INSERT .. VALUES (), VALUES (),
 VALUES () allow more efficient application designs. Enhancements to
 UPDATE and DELETE allow additional constructs for clarity and ease of
 use.
 
 SQL:2003 Analytical functions (Sergey, Tom, Neil)
 
   All statistical aggregate functions defined by SQL:2003 are now
 supported and user-defined aggregates now can take multiple columns as
 inputs.
 
 -- 
   Simon Riggs 
   EnterpriseDB   http://www.enterprisedb.com
 
 
 ---(end of broadcast)---
 TIP 4: Have you searched our list archives?
 
http://archives.postgresql.org

-- 
  Bruce Momjian   [EMAIL PROTECTED]
  EnterpriseDBhttp://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [HACKERS] Release Notes: Major Changes in 8.2

2006-09-20 Thread Josh Berkus
Bruce,

What happened to PL/pgSQL debugging?  Did it die?

-- 
Josh Berkus
PostgreSQL @ Sun
San Francisco

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match