Skip to content

Commit f706f2c

Browse files
committed
Update 9.4 release notes for commits through today.
Add entries for recent changes, including noting the JSONB format change and the recent timezone data changes. We should remove those two items before 9.4 final: the JSONB change will be of no interest in the long run, and it's not normally our habit to mention timezone updates in major-release notes. But it seems important to document them temporarily for beta testers. I failed to resist the temptation to wordsmith a couple of existing entries, too.
1 parent d0410d6 commit f706f2c

File tree

1 file changed

+81
-21
lines changed

1 file changed

+81
-21
lines changed

doc/src/sgml/release-9.4.sgml

Lines changed: 81 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,8 @@
77
<note>
88
<title>Release Date</title>
99
<simpara>2014-??-??</simpara>
10-
<simpara>Current as of 2014-08-17</simpara>
10+
<simpara>Current as of 2014-10-05</simpara>
11+
<!-- Be sure to remove "delta from 9.4beta" items below before final! -->
1112
</note>
1213

1314
<sect2>
@@ -89,6 +90,22 @@
8990

9091
<itemizedlist>
9192

93+
<!-- delta from 9.4beta2, be sure to remove before final: -->
94+
<listitem>
95+
<para>
96+
Change on-disk format of <type>jsonb</> data
97+
(Heikki Linnakangas and Tom Lane)
98+
</para>
99+
100+
<para>
101+
The on-disk representation was changed after 9.4beta2 to improve
102+
efficiency. <application>pg_upgrade</> will refuse to upgrade any
103+
9.4beta1 or 9.4beta2 database containing <type>jsonb</> columns; you
104+
will need to use <application>pg_dumpall</> instead to migrate such
105+
databases.
106+
</para>
107+
</listitem>
108+
92109
<listitem>
93110
<para>
94111
Tighten checks for multidimensional <link
@@ -224,18 +241,6 @@
224241
</para>
225242
</listitem>
226243

227-
<listitem>
228-
<para>
229-
Writable foreign data wrappers must return all columns when the foreign
230-
table has an <literal>AFTER ROW</> trigger (Noah Misch)
231-
</para>
232-
233-
<para>
234-
Previously, foreign tables never had triggers, and
235-
the <literal>RETURNING</> clause alone dictated the columns required.
236-
</para>
237-
</listitem>
238-
239244
<listitem>
240245
<para>
241246
Rename <link linkend="SQL-EXPLAIN"><command>EXPLAIN
@@ -265,6 +270,22 @@
265270
</para>
266271
</listitem>
267272

273+
<listitem>
274+
<para>
275+
Foreign data wrappers that support updating foreign tables must
276+
consider the possible presence of <literal>AFTER ROW</> triggers
277+
(Noah Misch)
278+
</para>
279+
280+
<para>
281+
When an <literal>AFTER ROW</> trigger is present, all columns of the
282+
table must be returned by updating actions, since the trigger might
283+
inspect any or all of them. Previously, foreign tables never had
284+
triggers, so the FDW might optimize away fetching columns not mentioned
285+
in the <literal>RETURNING</> clause (if any).
286+
</para>
287+
</listitem>
288+
268289
<listitem>
269290
<para>
270291
Prevent <link
@@ -389,6 +410,27 @@
389410
</para>
390411
</listitem>
391412

413+
<!-- delta from 9.4beta2, be sure to remove before final: -->
414+
<listitem>
415+
<para>
416+
Update time zone data files to tzdata release 2014h for DST law
417+
changes in Russia and elsewhere
418+
</para>
419+
420+
<para>
421+
This change is more significant than most time zone updates because
422+
many Russian zone abbreviations are changing meaning, including IRKT,
423+
KRAT, MAGT, MSK, NOVT, OMST, SAKT, VLAT, YAKT, and YEKT. Also, IANA
424+
has formally recognized abbreviations of the form
425+
A<replaceable>x</>ST/A<replaceable>x</>DT for Australian timezones,
426+
so adopt those names as part of the <quote>Default</> abbreviation
427+
set in <productname>PostgreSQL</>. The <quote>Australia</>
428+
abbreviation set now need be selected only if it's desired to use
429+
historical abbreviations that conflict with abbreviations commonly
430+
used elsewhere, such as EST or SAST.
431+
</para>
432+
</listitem>
433+
392434
</itemizedlist>
393435

394436
</sect2>
@@ -1099,6 +1141,14 @@
10991141
</para>
11001142
</listitem>
11011143

1144+
<listitem>
1145+
<para>
1146+
Ensure that <link linkend="SQL-SELECT"><literal>SELECT ... FOR UPDATE
1147+
NOWAIT</></link> does not wait in corner cases involving
1148+
already-concurrently-updated tuples (Craig Ringer and Thomas Munro)
1149+
</para>
1150+
</listitem>
1151+
11021152
</itemizedlist>
11031153

11041154
</sect3>
@@ -1257,11 +1307,9 @@
12571307
<listitem>
12581308
<para>
12591309
Allow moving groups of objects from one tablespace to another
1260-
using <literal>ALL IN TABLESPACE ... SET TABLESPACE</> with
1261-
<link linkend="SQL-ALTERTABLE"><command>ALTER TABLE</></link>
1262-
<link linkend="SQL-ALTERINDEX"><command>ALTER INDEX</></link> and
1263-
<link linkend="SQL-ALTERMATERIALIZEDVIEW"><command>ALTER MATERIALIZED VIEW</></link>
1264-
(Stephen Frost)
1310+
using the <literal>ALL IN TABLESPACE ... SET TABLESPACE</> form of
1311+
<xref linkend="SQL-ALTERTABLE">, <xref linkend="SQL-ALTERINDEX">, or
1312+
<xref linkend="SQL-ALTERMATERIALIZEDVIEW"> (Stephen Frost)
12651313
</para>
12661314
</listitem>
12671315

@@ -2498,9 +2546,21 @@
24982546
</para>
24992547

25002548
<para>
2501-
This allows monitoring tools to only fetch query text for newly
2502-
created entries, improving performance for repeated querying of the
2503-
statistics.
2549+
This allows monitoring tools to fetch query text only for
2550+
just-created entries, improving performance during repeated querying
2551+
of the statistics.
2552+
</para>
2553+
</listitem>
2554+
2555+
<listitem>
2556+
<para>
2557+
Make <application>pg_stat_statements</> ignore <command>DEALLOCATE</>
2558+
commands (Fabien Coelho)
2559+
</para>
2560+
2561+
<para>
2562+
It already ignored <command>PREPARE</>, as well as planning time in
2563+
general, so this seems more consistent.
25042564
</para>
25052565
</listitem>
25062566

0 commit comments

Comments
 (0)