... at
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=42de8a0255c2509bf179205e94b9d65f9d6f3cf9
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mail
On Thu, Mar 30, 2017 at 06:23:04PM -0400, Robert Haas wrote:
> Hi,
>
> One of the things we'll need to do to get 10beta1 out the door is have
> a set of release notes. I spoke with Bruce Momjian today at PGCONF.US
> and he told me that he has set aside time during April to write them
> and will b
Hi,
One of the things we'll need to do to get 10beta1 out the door is have
a set of release notes. I spoke with Bruce Momjian today at PGCONF.US
and he told me that he has set aside time during April to write them
and will begin working on it once we reach feature freeze. I think
this is good, b
Michael Paquier writes:
> This is obviously incorrect because recovery_min_apply_delay has been only
> introduced in 9.4. The culprit is visibly the commit message of 8049839 and
> others that mentioned the parameter, though the patch applied does nothing
> about it. Please see attached a patch to
Hi all,
While doing a git grep on recovery_min_apply_delay I noticed the following:
$ git grep recovery_min_apply -- *release*.sgml
src/sgml/release-9.0.sgml: that recovery_min_apply_delay
failed to delay application
src/sgml/release-9.1.sgml: that recovery_min_apply_delay
failed to dela
I've committed the release notes for today's releases, if anyone wants
to take a look. Fortunately, there's not much to them. Unfortunately,
I need to start the wrap process in about an hour, so there's not much
time to review either :-(
regards, tom lane
--
Sent via p
On 01/27/2015 10:17 AM, Tom Lane wrote:
Andres Freund writes:
On 2015-01-27 10:09:12 -0800, Joshua D. Drake wrote:
Where can one find the running copy of release notes for pending releases?
In the source tree on the master once it exists. It doesn't yet for the
next set of releases.
The
Andres Freund writes:
> On 2015-01-27 10:09:12 -0800, Joshua D. Drake wrote:
>> Where can one find the running copy of release notes for pending releases?
> In the source tree on the master once it exists. It doesn't yet for the
> next set of releases.
The closest thing to a "running copy" is th
On 2015-01-27 10:09:12 -0800, Joshua D. Drake wrote:
> Where can one find the running copy of release notes for pending releases?
In the source tree on the master once it exists. It doesn't yet for the
next set of releases.
Greetings,
Andres Freund
--
Andres Freund http://
Where can one find the running copy of release notes for pending releases?
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, @cmdpromptinc
"If we send our children to Caes
Marti Raudsepp writes:
> The 9.2.3 release notes say:
> * Fix pg_upgrade's -O/-o options (Bruce Momjian)
> You got it the wrong way around, he was the one who introduced the bug! ;)
Sorry about that. The release notes are made based on commit-log
entries. In this case we had
Author: Bruce Mom
On 8 February 2013 09:43, Marti Raudsepp wrote:
> No big deal, it was just one space, but I wanted to voice my
> disagreement with how Postgres committers don't retain original patch
> authorship information.
I agree its very important to get that right.
It's important for the PostgreSQL projec
Hi,
The 9.2.3 release notes say:
* Fix pg_upgrade's -O/-o options (Bruce Momjian)
You got it the wrong way around, he was the one who introduced the bug! ;)
I originally found, debugged and provided the fix:
http://www.postgresql.org/message-id/cabrt9rby1urtmy-dfldgbpcp+zqu36m_+bld4wfwugohg-m...
[Sorry for the delay. I'd stopped checking the pgsql mailing lists.
Thanks to David Wheeler and Josh Berkus for the heads-up.]
On Sun, May 30, 2010 at 06:58:32PM -0400, Andrew Dunstan wrote:
>
> Tim Bunce wrote:
> >On Mon, May 17, 2010 at 11:34:37AM -0400, Tom Lane wrote:
> >>Andrew Dunstan writ
On Sun, May 30, 2010 at 6:58 PM, Andrew Dunstan wrote:
> Tim Bunce wrote:
>> p.s. It also turned to be insufficiently useful for NYTProf since it
>> doesn't also update some internals to record the 'filename' and line
>> number range of the sub. So PostgreSQL::PLPerl::NYTProf works around
>> that
Tim Bunce wrote:
On Mon, May 17, 2010 at 11:34:37AM -0400, Tom Lane wrote:
Andrew Dunstan writes:
Why do the release notes say this, under plperl:
* PL/Perl subroutines are now given names (Tim Bunce)
This is for the use of profiling and code coverage tools. DIDN'T
TH
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > Andrew Dunstan writes:
> >
> >> OK ... I guess I was bothered because this has been referred to in a
> >> public press release about the Beta. The PLPerl security stuff is
> >> missing too, so I'll fix that also.
> >>
> >
> > The security
On Mon, May 17, 2010 at 11:34:37AM -0400, Tom Lane wrote:
> Andrew Dunstan writes:
> > Why do the release notes say this, under plperl:
> > * PL/Perl subroutines are now given names (Tim Bunce)
> > This is for the use of profiling and code coverage tools. DIDN'T
> > THEY HAVE NAMES
Tom Lane wrote:
Andrew Dunstan writes:
OK ... I guess I was bothered because this has been referred to in a
public press release about the Beta. The PLPerl security stuff is
missing too, so I'll fix that also.
The security stuff isn't relevant to the 9.0 notes, since it's already
b
Andrew Dunstan writes:
> OK ... I guess I was bothered because this has been referred to in a
> public press release about the Beta. The PLPerl security stuff is
> missing too, so I'll fix that also.
The security stuff isn't relevant to the 9.0 notes, since it's already
been fixed in a previous
Tom Lane wrote:
Andrew Dunstan writes:
Why do the release notes say this, under plperl:
* PL/Perl subroutines are now given names (Tim Bunce)
This is for the use of profiling and code coverage tools. DIDN'T
THEY HAVE NAMES BEFORE?
If whoever put this in the releas
Andrew Dunstan writes:
> Why do the release notes say this, under plperl:
> * PL/Perl subroutines are now given names (Tim Bunce)
> This is for the use of profiling and code coverage tools. DIDN'T
> THEY HAVE NAMES BEFORE?
> If whoever put this in the release notes had bothered to
Why do the release notes say this, under plperl:
* PL/Perl subroutines are now given names (Tim Bunce)
This is for the use of profiling and code coverage tools. DIDN'T
THEY HAVE NAMES BEFORE?
No they didn't, from perl's perspective, which is what this is about.
They had names fro
"Erik Rijkers" writes:
> In 9.0devel cvs, I can find & affirm the SIMILAR TO changes, but I cannot
> find any changes to
> substring() (other than the one under point 3.)
What's affected is the three-parameter form of SUBSTRING(). See
section 9.7.2.
The second of these is still wrong, though,
In the 9.0devel release notes
http://developer.postgresql.org/pgdocs/postgres/release-9-0.html
under
E.1.2.3. String Handling
three changes are mentioned, and for the first two changes it is said that
substring() is "affected":
8<
1
Properly treat ^ and $ as lite
Hello
"PL/pgSQL functions using RETURNS QUERY or RECORD types no longer
always need to be rebuilt after adding or dropping a column for the
related tables."
I thing, so this isn't correct. When you dropped column, then you had
to rebuild table - rebuild related function had no effect.
Regards
P
>>> On Thu, Oct 18, 2007 at 12:34 AM, in message
<[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> This release represents a major leap forward for PostgreSQL by adding
> significant new functionality and performance enhancements. This was
> made possible by a growing community that
D'Arcy J.M. Cain wrote:
> On Thu, 11 Oct 2007 16:34:14 -0400 (EDT)
> Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > Kevin Grittner wrote:
> > > > PostgreSQL. Many complex ideas that normally take years
> > > > to implement were added rapidly to this release by our development team.
> > >
> > > You
Kevin Grittner wrote:
How exactly do you expect the software to get from a .0 to a .1 release,
or to have addressed the bugs that might bite you when it does get to .1,
if you aren't helping to test it?
In most environments I've seen, developer and QA systems don't hesitate
to move to .0
>>> On Fri, Oct 12, 2007 at 12:37 PM, in message
<[EMAIL PROTECTED]>, Ron Mayer
<[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
>> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>>> With respect to you Kevin, your managers should wait. You don't
>>> install .0 releases of "any" software into productio
Tom Lane wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> With respect to you Kevin, your managers should wait. You don't
>> install .0 releases of "any" software into production without "months"
>> of testing. At which point, normally a .1 release has come out anyway.
>
> How exactly do
On Fri, Oct 12, 2007 at 07:51:13AM +0100, Simon Riggs wrote:
> On Thu, 2007-10-11 at 17:46 -0400, Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> > > Kevin Grittner wrote:
> > >> If the goal is to provide fair warning of a high-than-usual-risk
> > >> release, you've got it covered.
On Thu, 2007-10-11 at 17:46 -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Kevin Grittner wrote:
> >> If the goal is to provide fair warning of a high-than-usual-risk
> >> release, you've got it covered.
>
> > No, that was not the intent. The indent was to say we got a lot
On Thu, 11 Oct 2007 21:31:20 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> > With respect to you Kevin, your managers should wait. You don't
>
> Now I realize that you did say "test" above, but way too often I see
> this sort of argument as a justifi
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> With respect to you Kevin, your managers should wait. You don't
> install .0 releases of "any" software into production without "months"
> of testing. At which point, normally a .1 release has come out anyway.
How exactly do you expect the software t
On Oct 11, 2007, at 18:51 , Joshua D. Drake wrote:
With respect to you Kevin, your managers should wait. You don't
install .0 releases of "any" software into production without "months"
of testing. At which point, normally a .1 release has come out anyway.
At the same time, an open source pro
On Thu, 11 Oct 2007 15:26:43 -0500
"Kevin Grittner" <[EMAIL PROTECTED]> wrote:
> > This release represents a major leap forward by adding significant
> > new functionality and performance enhancements to
> > PostgreSQL. Many complex ideas that normally take
> > years to implement were added rapidl
>>> On Thu, Oct 11, 2007 at 3:34 PM, in message
<[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> The indent was to say we got a lot done in
> one year. You have a suggestion?
My suggestion would be to stay away from statements about the speed
of development and focus on the user
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Kevin Grittner wrote:
>> If the goal is to provide fair warning of a high-than-usual-risk
>> release, you've got it covered.
> No, that was not the intent. The indent was to say we got a lot done in
> one year. You have a suggestion?
Yeah: take the ent
On 10/11/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Kevin Grittner wrote:
> > >>> On Thu, Oct 11, 2007 at 3:04 PM, in message
> > <[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]>
> wrote:
> >
> > > This release represents a major leap forward by adding significant new
> > > functionali
On Thu, 2007-10-11 at 16:04 -0400, Bruce Momjian wrote:
> I have added the following introductory paragraph to the release notes:
>
> This release represents a major leap forward by adding significant new
> functionality and performance enhancements to
> PostgreSQL. Many complex
On Thu, 11 Oct 2007 16:34:14 -0400 (EDT)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Kevin Grittner wrote:
> > > PostgreSQL. Many complex ideas that normally take years
> > > to implement were added rapidly to this release by our development team.
> >
> > You do realize that this will make many ma
Kevin Grittner wrote:
> >>> On Thu, Oct 11, 2007 at 3:04 PM, in message
> <[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> > This release represents a major leap forward by adding significant new
> > functionality and performance enhancements to
> > PostgreSQL. Many complex idea
>>> On Thu, Oct 11, 2007 at 3:04 PM, in message
<[EMAIL PROTECTED]>, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> This release represents a major leap forward by adding significant new
> functionality and performance enhancements to
> PostgreSQL. Many complex ideas that normally take years
> to im
[ BCC to docs and hackers. Sorry this seems like the only logical way
to do this.]
I have added the following introductory paragraph to the release notes:
This release represents a major leap forward by adding significant new
functionality and performance enhancements to
Gregory Stark wrote:
>
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>
> > Asynchronous Commit allows some transactions to commit faster than
> > others, offering a trade-off between performance and durability for
> > specific transaction types only
>
> A lot of users will be confused about what a
On Fri, 2007-10-05 at 11:24 +0100, Gregory Stark wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>
> > Asynchronous Commit allows some transactions to commit faster than
> > others, offering a trade-off between performance and durability for
> > specific transaction types only
>
> A lot of use
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Asynchronous Commit allows some transactions to commit faster than
> others, offering a trade-off between performance and durability for
> specific transaction types only
A lot of users will be confused about what asynchronous commit does. I think
it's
My suggested edit of the Overview section of the Release Notes. The
emphasis is on user-noticeable features, so some of the major internal
changes are lower down the list. Some items have been removed or placed
below the performance features.
New data types for SQL/XML, enum and uuid types
Updat
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
Markus Schaber wrote:
-- Start of PGP signed section.
> 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
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."
HTH,
Markus
--
Markus Schaber | Logical Tracking&Trac
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 deta
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 inf
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 enha
> -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 w
> -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
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
> >>Postg
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
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 o
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 enhancemen
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
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 relat
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
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
[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
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,
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 bug
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 usefu
> -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
&
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
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]
En
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 "br
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 tunin
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
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
Simon Riggs wrote:
> On Fri, 2006-09-15 at 15:37 -0400, Bruce Momjian wrote:
> > I have completed my first pass over the release notes and Tom has made
> > some additions:
> >
> > http://momjian.postgresql.org/cgi-bin/pgrelease
> >
> > I will probably go over them again in a few hours, update
Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Wed, Sep 20, 2006 at 05:10:13PM +0100, Simon Riggs wrote:
> > > Also, not sure what the thoughts are regarding surnames. I'm referred to
> > > as both Simon and Simon Riggs in the release notes. Should we have a
> > > policy of first mention uses fu
Jim C. Nasby wrote:
> On Wed, Sep 20, 2006 at 05:10:13PM +0100, Simon Riggs wrote:
> > Also, not sure what the thoughts are regarding surnames. I'm referred to
> > as both Simon and Simon Riggs in the release notes. Should we have a
> > policy of first mention uses full name, subsequent mentions ju
On Wed, Sep 20, 2006 at 05:10:13PM +0100, Simon Riggs wrote:
> Also, not sure what the thoughts are regarding surnames. I'm referred to
> as both Simon and Simon Riggs in the release notes. Should we have a
> policy of first mention uses full name, subsequent mentions just use
> first name if there
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
Pro
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 dist
"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
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 data
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?
N
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
On Fri, 2006-09-15 at 15:37 -0400, Bruce Momjian wrote:
> I have completed my first pass over the release notes and Tom has made
> some additions:
>
> http://momjian.postgresql.org/cgi-bin/pgrelease
>
> I will probably go over them again in a few hours, update them to
> current CVS, then mo
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:
Thanks, done.
---
Alvaro Herrera wrote:
> Jim C. Nasby wrote:
> > On Tue, Sep 19, 2006 at 09:37:39AM -0400, Bruce Momjian wrote:
> > > Jim C. Nasby wrote:
> > > > On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote
Jim C. Nasby wrote:
> On Tue, Sep 19, 2006 at 09:37:39AM -0400, Bruce Momjian wrote:
> > Jim C. Nasby wrote:
> > > On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote:
> > > > > Both this and pg_prepared_statements are very useful for pooled
> > > > > connection setups."
> > > > >
> > >
On Tue, Sep 19, 2006 at 09:37:39AM -0400, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote:
> > > > Both this and pg_prepared_statements are very useful for pooled
> > > > connection setups."
> > > >
> > > > Should read "Both of these are
Jim C. Nasby wrote:
> On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote:
> > > Both this and pg_prepared_statements are very useful for pooled
> > > connection setups."
> > >
> > > Should read "Both of these are very useful..."
> >
> > I don't think I can't change that because they ar
On Mon, Sep 18, 2006 at 06:47:02PM -0400, Bruce Momjian wrote:
> > Both this and pg_prepared_statements are very useful for pooled
> > connection setups."
> >
> > Should read "Both of these are very useful..."
>
> I don't think I can't change that because they are two separate bullet
> items.
E
Jim C. Nasby wrote:
> I couldn't remember if you wanted grammar/spelling nitpicks, so I
> included them... sorry for the noise if you didn't want them.
>
> #Improve performance of statistics monitoring, especially
> pg_stat_activity (Tom)#
>
> I would s/pg_stat_activity/stats_command_string/, sin
I couldn't remember if you wanted grammar/spelling nitpicks, so I
included them... sorry for the noise if you didn't want them.
#Improve performance of statistics monitoring, especially
pg_stat_activity (Tom)#
I would s/pg_stat_activity/stats_command_string/, since that's where the
actual change
Teodor Sigaev wrote:
> I see two entries:
> * Improve subtransaction performance (Alvaro, Itagaki Takahiro, Tom)
> * Improve sub-transaction performance (Itagaki Takahiro)
> Aren't they the same?
Yes, removed.
> Markup: New operators for array-subset comparisons (<@, @>, &&)
Yes, that
I see two entries:
* Improve subtransaction performance (Alvaro, Itagaki Takahiro, Tom)
* Improve sub-transaction performance (Itagaki Takahiro)
Aren't they the same?
Markup: New operators for array-subset comparisons (<@, @>, &&)
--
Teodor Sigaev E-ma
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have completed my first pass over the release notes and Tom has made
> > some additions:
> >
> > http://momjian.postgresql.org/cgi-bin/pgrelease
> >
> > I will probably go over them again in a few hours, update them to
> > current CVS, then m
Bruce Momjian wrote:
> I have completed my first pass over the release notes and Tom has made
> some additions:
>
> http://momjian.postgresql.org/cgi-bin/pgrelease
>
> I will probably go over them again in a few hours, update them to
> current CVS, then move them into our SGML documentation
1 - 100 of 160 matches
Mail list logo
