Horton

Re: PG 12 draft release notes

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Bruce Momjian <bruce@momjian.us>, Andrew Gierth <andrew@tao11.riddles.org.uk>, Emre Hasegeli <emre@hasegeli.com>, Tomas Vondra <tv@fuzzy.cz>, Peter Geoghegan <pg@bowt.ie>, Alexander Korotkov <aekorotkov@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Peter Eisentraut <peter_e@gmx.net>, Surafel Temesgen <surafel3000@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2019-05-20T22:56:50Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. doc: PG 12 relnotes: update wording on truncate/vacuum item

  2. docs: PG 12 relnotes, update btree items

  3. doc: PG 12 relnotes, list added snowball/FTS languages

  4. doc: PG 12 relnotes, merge new SQL partition function items

  5. docs: PG 12 release notes, support functions

  6. docs: PG 12 relnote adjustments based on feedback from Tom Lane

  7. docs: adjust RECORD PG 12 relnote item

  8. doc: adjust PG 12 relnotes item on float digit adjustment

  9. doc: adjustments for PG 12 release notes

  10. docs: fix duplicate wording in PG 12 release notes

  11. doc: properly attibute PG 12 pgbench release note item

  12. doc: PG 12 release notes: normalize attribution names

  13. Refactor the fsync queue for wider use.

  14. Add "split after new tuple" nbtree optimization.

  15. Add nbtree high key "continuescan" optimization.

  16. Allow amcheck to re-find tuples using new search.

  17. Consider secondary factors during nbtree splits.

  18. Partial implementation of SQL/JSON path language

  19. Allow extensions to generate lossy index conditions.

  20. Make TupleTableSlots extensible, finish split of existing slot type.

  21. Reduce path length for locking leaf B-tree pages during insertion

Andres Freund <andres@anarazel.de> writes:
> Note that I've added a few questions to individuals involved with
> specific points. If you're in the To: list, please search for your name.

I'm not sure which of my commits you want me to opine on, other than

>      <listitem>
> <!--
> Author: Tom Lane <tgl@sss.pgh.pa.us>
> 2019-01-30 [5f5c01459] Allow RECORD and RECORD[] to be specified in function co
> -->
>       <para>
>        Allow <type>RECORD</type> and <type>RECORD[]</type> to be specified
>        as a function <link linkend="sql-createfunction">return-value
>        record</link> (Elvis Pranskevichus)
>       </para>
>       <para>
>        DETAIL?
>       </para>
>      </listitem>

> This description doesn't sound accurate to me. Tom?

Yeah, maybe better

       Allow <type>RECORD</type> and <type>RECORD[]</type> to be used
       as column types in a query's column definition list for a
       table function that is declared to return <type>RECORD</type>
       (Elvis Pranskevichus)

You could link to "queries-tablefunctions" which describes the column
definition business; it's much more specific than "sql-createfunction".

			regards, tom lane