public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Yugo NAGATA <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: First draft of PG 17 release notes
Date: Mon, 7 Oct 2024 19:25:11 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Mon, Sep 30, 2024 at 02:20:21PM +0900, Yugo NAGATA wrote:
> On Sat, 28 Sep 2024 21:19:11 -0400
> Bruce Momjian <[email protected]> wrote:
>
> > On Thu, Sep 26, 2024 at 02:19:21PM +0900, Yugo Nagata wrote:
> > > On Thu, 9 May 2024 00:03:50 -0400
> > > Bruce Momjian <[email protected]> wrote:
> > >
> > > > I have committed the first draft of the PG 17 release notes; you can
> > > > see the results here:
> > >
> > > I propose to improve the following description in "Migration to Version 17"
> > > section by adding CREATE INDEX and CREATE MATERIALIZED VIEW into the command list.
> > >
> > > <para>
> > > Change functions to use a safe <xref linkend="guc-search-path"/>
> > > during maintenance operations (Jeff Davis)
> > > <ulink url="&commit_baseurl;2af07e2f7">§</ulink>
> > > </para>
> > >
> > > It is suggested in the thread [1] that users could not notice the behaviour
> > > of CREATE INDEX is changed because the explicit command name is not listed in
> > > the release notes. So, I think it is better to add CREATE INDEX and
> > > CREATE MATERIALIZED VIEW into the command list.
> > >
> > > I've attached a patch.
> >
> > It this a valid change? Seems so.
>
> Yes. This change on CREATE INDEX was introduced by 2af07e2f7 together with
> other commands, but it was missed to be mentioned in the commit message
> although the description was added to the documentation.
>
> The change on CEATE MATERIALIZED VIEW was introduced by a separate commit
> b4da732fd, since which the REFRESH logic is used when creating a matview.
> Should we add here a link to that commit, too?
I developed the attached patch which adds the two commands and the
commit item.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
Attachments:
[text/x-diff] REL_17_STABLE_schema.diff (1.0K, ../[email protected]/2-REL_17_STABLE_schema.diff)
download | inline diff:
diff --git a/doc/src/sgml/release-17.sgml b/doc/src/sgml/release-17.sgml
index ad814737745..7acdee05e42 100644
--- a/doc/src/sgml/release-17.sgml
+++ b/doc/src/sgml/release-17.sgml
@@ -125,6 +125,8 @@
<!--
Author: Jeff Davis <[email protected]>
2024-03-04 [2af07e2f7] Fix search_path to a safe value during maintenance opera
+Author: Jeff Davis <[email protected]>
+2024-07-16 [b4da732fd64] When creating materialized views, use REFRESH to load data.
-->
<listitem>
@@ -136,7 +138,9 @@ Author: Jeff Davis <[email protected]>
<para>
This prevents maintenance operations (<command>ANALYZE</command>,
- <command>CLUSTER</command>, <command>REFRESH
+ <command>CLUSTER</command>, <command>CREATE
+ INDEX</command>, <command>CREATE
+ MATERIALIZED VIEW</command>, <command>REFRESH
MATERIALIZED VIEW</command>, <command>REINDEX</command>,
or <command>VACUUM</command>) from performing unsafe access.
Functions used by expression indexes and materialized views that
view thread (146+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: First draft of PG 17 release notes
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox