On Thu, May 10, 2012 at 10:50:14AM +0300, Heikki Linnakangas wrote:
> On 10.05.2012 06:11, Bruce Momjian wrote:
> >I have completed my draft of the 9.2 release notes, and committed it to
> >git.
> 
> Thanks! I committed a few trivial fixes, below are a few more I
> wasn't sure about:
> 
> >* Add support for range data types (Jeff Davis, Tom Lane, Alexander Korotkov)
> >
> >The range data type records a lower and upper bound, and supports 
> >comparisons like contains, overlaps, and intersection.
> 
> /s/comparisons/operations/ ?
> 
> >* Allow a user to cancel queries in other owned sessions using 
> >pg_cancel_backend() (Magnus Hagander)
> >
> >Previously only the superuser could cancel queries.
> 
> "other owned sessions" is a bit ambiguous. It reads to me like
> "possessed sessions" or "0wned sessions". It's not clear it means
> sessions owned by the same user. How about "... to cancel queries in
> his other sessions, using ..." ? Or:
> 
> * Allow a non-superuser to cancel queries in another backend using
> pg_cancel_backend(), as long as the victim backend belongs to the
> same user
> 
> Previously only the superuser could cancel queries.
> 
> 
> >* Change default names of triggers to fire action triggers before check 
> >triggers (Tom Lane)
> >
> >This allows default-named check triggers to check post-action rows.
> 
> That's quite a mouthful :-). I don't understand what it means.
> 
> >In psql tab completion, complete SQL key words based on COMP_KEYWORD_CASE 
> >setting and the perhaps case of the partially-supplied word (Peter 
> >Eisentraut, Fujii Masao)
> 
> Which is correct spelling, "keyword" or "key word"? We seem to use
> both in the docs. "Keyword" sounds much better to me, but I think I
> might be more prone to write words together than native English
> speakers.

I have made adjustments based on your comments in the attached, applied
patch.

-- 
  Bruce Momjian  <br...@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
new file mode 100644
index 86a4e04..d63b572
*** a/doc/src/sgml/release-9.2.sgml
--- b/doc/src/sgml/release-9.2.sgml
***************
*** 1567,1573 ****
         
         <para>
          The range data type records a lower and upper bound, and supports
!         comparisons like contains, overlaps, and intersection.
         </para>
        </listitem>
        
--- 1567,1573 ----
         
         <para>
          The range data type records a lower and upper bound, and supports
!         operations like contains, overlaps, and intersection.
         </para>
        </listitem>
        
***************
*** 1659,1665 ****
  
        <listitem>
         <para>
!         Allow a user to cancel queries in other owned sessions using <link
          linkend="functions-admin-signal"><function>pg_cancel_backend()</></link>
          (Magnus Hagander)
         </para>
--- 1659,1665 ----
  
        <listitem>
         <para>
!         Allow users to cancel queries in user-matching sessions using <link
          linkend="functions-admin-signal"><function>pg_cancel_backend()</></link>
          (Magnus Hagander)
         </para>
***************
*** 1730,1737 ****
  
        <listitem>
         <para>
!         Change default names of triggers to fire action triggers before
!         check triggers (Tom Lane)
         </para>
         
         <para>
--- 1730,1737 ----
  
        <listitem>
         <para>
!         Change default names of triggers to fire "action" triggers before
!         "check" triggers (Tom Lane)
         </para>
         
         <para>
***************
*** 2229,2235 ****
        <listitem>
         <para>
          In <application>psql</> tab completion,
!         complete <acronym>SQL</acronym> key words based on
          <varname>COMP_KEYWORD_CASE</> setting and the perhaps case of
          the partially-supplied word (Peter Eisentraut, Fujii Masao)
         </para>
--- 2229,2235 ----
        <listitem>
         <para>
          In <application>psql</> tab completion,
!         complete <acronym>SQL</acronym> keywords based on
          <varname>COMP_KEYWORD_CASE</> setting and the perhaps case of
          the partially-supplied word (Peter Eisentraut, Fujii Masao)
         </para>
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to