Re: PG 12 draft release notes
Bruce Momjian <bruce@momjian.us>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
doc: PG 12 relnotes: update wording on truncate/vacuum item
- 4f41a7227511 12.0 landed
-
docs: PG 12 relnotes, update btree items
- 4bfb79ff6b1f 12.0 landed
-
doc: PG 12 relnotes, list added snowball/FTS languages
- 968072837173 12.0 landed
-
doc: PG 12 relnotes, merge new SQL partition function items
- 6a631a454664 12.0 landed
-
docs: PG 12 release notes, support functions
- 728840fe13ac 12.0 landed
-
docs: PG 12 relnote adjustments based on feedback from Tom Lane
- 8e719d33fd25 12.0 landed
-
docs: adjust RECORD PG 12 relnote item
- 3468a04a3e49 12.0 landed
-
doc: adjust PG 12 relnotes item on float digit adjustment
- b84a801d6a67 12.0 landed
-
doc: adjustments for PG 12 release notes
- 32fe2e3194c7 12.0 landed
-
docs: fix duplicate wording in PG 12 release notes
- 34d40becfa7a 12.0 landed
-
doc: properly attibute PG 12 pgbench release note item
- 5d971565a799 12.0 landed
-
doc: PG 12 release notes: normalize attribution names
- f86b0c3c4653 12.0 landed
-
Refactor the fsync queue for wider use.
- 3eb77eba5a51 12.0 cited
-
Add "split after new tuple" nbtree optimization.
- f21668f328c8 12.0 cited
-
Add nbtree high key "continuescan" optimization.
- 29b64d1de7c7 12.0 cited
-
Allow amcheck to re-find tuples using new search.
- c1afd175b5b2 12.0 cited
-
Consider secondary factors during nbtree splits.
- fab250243387 12.0 cited
-
Partial implementation of SQL/JSON path language
- 72b6460336e8 12.0 cited
-
Allow extensions to generate lossy index conditions.
- 74dfe58a5927 12.0 cited
-
Make TupleTableSlots extensible, finish split of existing slot type.
- 4da597edf1ba 12.0 cited
-
Reduce path length for locking leaf B-tree pages during insertion
- d2086b08b023 12.0 cited
On Mon, May 20, 2019 at 06:56:50PM -0400, Tom Lane wrote: > 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". Done. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +