On mån, 2009-08-17 at 14:29 -0700, Josh Berkus wrote:
> Since I'd need to install haskell on my system before installing pandoc,
> I've attached my "final" edit of the RST file so that I don't hold
> things up.
committed that
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
Peter,
Since I'd need to install haskell on my system before installing pandoc,
I've attached my "final" edit of the RST file so that I don't hold
things up.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
.. -*- mode: rst -*-
=
Release 8.5alpha1
=
Overv
On mån, 2009-08-17 at 10:39 -0700, Josh Berkus wrote:
> Peter,
>
> Attached is a new draft of the "release notes".
>
> What I've done in this version is added more subsections and arranged
> stuff into groups by funcitonality area. I think this makes the notes
> vastly easier to scan; having 25
Josh Berkus writes:
> Also, does the ADD/DROP COLUMN plpgsql patch fix any cases other than
> RETURNS QUERY? I can't tell from the patch.
Yes, I believe it does, but hadn't bothered to work up any test cases.
The places it touched in plpgsql are
* returning a single composite value
Tom,
> Actually, present tense is our general style for the release notes, and
> I had carefully made them all present tense ;-). It doesn't appear to
> me that you've been consistent about it here anyway.
OK, switching back to present tense then.
Does anyone else see anything missing?
Also, d
Josh Berkus writes:
> Particularly, we seemed to vacillate between present and past tense for
> the patch descriptions. I have changed all to past tense.
Actually, present tense is our general style for the release notes, and
I had carefully made them all present tense ;-). It doesn't appear to
Josh Berkus writes:
> On 8/17/09 11:51 AM, Tom Lane wrote:
>> I went over this quickly, and attach an updated version. This is
>> updated to current CVS HEAD, and wordsmithed a little bit, and I removed
>> some things that didn't seem worth documenting. In particular, the
>> introduction claims
All,
New version, incorporating Tom's changes and some additional reordering.
Particularly, we seemed to vacillate between present and past tense for
the patch descriptions. I have changed all to past tense.
Also, should we be adding patch author names to these notes?
--
Josh Berkus
PostgreS
On 8/17/09 11:51 AM, Tom Lane wrote:
> I went over this quickly, and attach an updated version. This is
> updated to current CVS HEAD, and wordsmithed a little bit, and I removed
> some things that didn't seem worth documenting. In particular, the
> introduction claims that back-patched bug fixes
Josh Berkus writes:
> Attached is a new draft of the "release notes".
I went over this quickly, and attach an updated version. This is
updated to current CVS HEAD, and wordsmithed a little bit, and I removed
some things that didn't seem worth documenting. In particular, the
introduction claims
Peter,
Attached is a new draft of the "release notes".
What I've done in this version is added more subsections and arranged
stuff into groups by funcitonality area. I think this makes the notes
vastly easier to scan; having 25 items generically under "server" wasn't
helpful at all to find featu
Tom Lane wrote:
> "Massa, Harald Armin" writes:
> > within source code, build options there is:
> > - Reserve the shared memory region during backend startup on Windows,
> > so that memory allocated by starting third party DLLs doesn't end up
> > conflicting with it. Hopefully this solves the
Alvaro Herrera writes:
> Tom Lane wrote:
>> In any case, it is not the function of the alpha release notes to
>> discuss changes in earlier release branches. The reason the commit
>> log points out the back-patch is to make it easier to extract the
>> information when we prepare release notes for
Tom Lane wrote:
> In any case, it is not the function of the alpha release notes to
> discuss changes in earlier release branches. The reason the commit
> log points out the back-patch is to make it easier to extract the
> information when we prepare release notes for the back-branch updates.
Hm
"Massa, Harald Armin" writes:
> within source code, build options there is:
> - Reserve the shared memory region during backend startup on Windows,
> so that memory allocated by starting third party DLLs doesn't end up
> conflicting with it. Hopefully this solves the long-time issue with
>
On Thursday 13 August 2009 17:07:38 Alvaro Herrera wrote:
> I wonder if this format can be converted to SGML DocBook automatically.
Yes, that's why I used it.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
Dimitri Fontaine wrote:
>
> Hi,
>
> Josh Berkus writes:
> > Will do. Teaching myself RST now
>
> I've been doing a lot of RST editing before, and found it pretty
> straightforward. Except for default table handling, where ascii-art
> maintenance is a pain, or you have to use extended tool
within source code, build options there is:
- Reserve the shared memory region during backend startup on Windows,
so that memory allocated by starting third party DLLs doesn't end up
conflicting with it. Hopefully this solves the long-time issue with
"could not reattach to shared memory" er
Hi,
Josh Berkus writes:
> Will do. Teaching myself RST now
I've been doing a lot of RST editing before, and found it pretty
straightforward. Except for default table handling, where ascii-art
maintenance is a pain, or you have to use extended tools, like emacs
table mode and such. Or use
On 8/12/09 11:13 AM, Peter Eisentraut wrote:
> On Wednesday 12 August 2009 19:27:06 Josh Berkus wrote:
>>> Can you export DocBook from that?
>> Not without writing some custom perl code, no.
>>
>> Should we stick your release notes on git somewhere? I'd like to expand
>> the and add a couple of th
On Wednesday 12 August 2009 19:27:06 Josh Berkus wrote:
> > Can you export DocBook from that?
>
> Not without writing some custom perl code, no.
>
> Should we stick your release notes on git somewhere? I'd like to expand
> the and add a couple of things.
I say just take the file and edit it.
--
> Can you export DocBook from that?
Not without writing some custom perl code, no.
Should we stick your release notes on git somewhere? I'd like to expand
the and add a couple of things.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-h
On Wednesday 12 August 2009 03:34:22 Josh Berkus wrote:
> On 8/11/09 3:27 PM, Peter Eisentraut wrote:
> > OK, since there was no clear consensus or volunteer for preparing release
> > notes for alpha 1, I have started something. Let me know what you think.
>
> Actually, the "consensus" was that Br
Robert Haas writes:
> Hmm, I thought we had some examples in there, but now that I look we
> only have an example for COSTS OFF, not for FORMAT. That does seem
> like an oversight.
I thought about adding one when I committed the patch, but concluded
that there was no point until the output forma
On Tue, Aug 11, 2009 at 8:32 PM, Alvaro
Herrera wrote:
> Mike wrote:
>
>> The thing that caused me the most trouble was that the "," wasn't very
>> noticeable sitting near the end of this line:
>>
>> EXPLAIN [ ( { ANALYZE boolean | VERBOSE boolean | COSTS boolean |
>> FORMAT { TEXT | XML | JSON } }
On 8/11/09 3:27 PM, Peter Eisentraut wrote:
> OK, since there was no clear consensus or volunteer for preparing release
> notes for alpha 1, I have started something. Let me know what you think.
Actually, the "consensus" was that Bruce was not going to share, so
Robert and I didn't want to bothe
Mike wrote:
> The thing that caused me the most trouble was that the "," wasn't very
> noticeable sitting near the end of this line:
>
> EXPLAIN [ ( { ANALYZE boolean | VERBOSE boolean | COSTS boolean |
> FORMAT { TEXT | XML | JSON } } [, ...] ) ] statement
>
> It may just be me, but I read that
If I didn't read this email I would still be trying to figure out how
to use the explain XML patch. Thanks Albert.
I found the syntax for the explain xml format to be quite difficult to
understand at first, it would be nice to give an example or two, ie:
EXPLAIN (ANALYZE, FORMAT XML) SELECT * FRO
A Dimecres, 12 d'agost de 2009, Peter Eisentraut va escriure:
> OK, since there was no clear consensus or volunteer for preparing release
> notes for alpha 1, I have started something. Let me know what you think.
>
> (reStructuredText, if you want to play around)
Maybe I'd be interesting to add d
OK, since there was no clear consensus or volunteer for preparing release
notes for alpha 1, I have started something. Let me know what you think.
(reStructuredText, if you want to play around)
.. -*- mode: rst -*-
=
Release 8.5alpha1
=
.. last commit: Simplify an
30 matches
Mail list logo
