Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfp3K-0000iS-4t for pgsql-admin@arkaria.postgresql.org; Tue, 25 Jun 2019 17:16:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hfp3J-0004il-1E for pgsql-admin@arkaria.postgresql.org; Tue, 25 Jun 2019 17:16:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfp3I-0004er-Jp for pgsql-admin@lists.postgresql.org; Tue, 25 Jun 2019 17:16:16 +0000 Received: from mr85p00im-hyfv06011301.me.com ([17.58.23.184]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hfp3G-0007yG-GD for pgsql-admin@lists.postgresql.org; Tue, 25 Jun 2019 17:16:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1561482973; bh=/5HVSvsXZTm9Kn5eylo+STGMSO5jRsHvxsL6YhUXK7o=; h=From:Content-Type:Mime-Version:Subject:Date:To:Message-Id; b=bZdBPvdpB3ibhAy5CRCzUfPS9nir1JcZhHHD1YZ+1lWfrHd+tviPWA/3zMAZIh8Hp dt6siIEroQQauDNlt24p2K88IlIOMlt/9gxQFQUROZwYzefl9RTervgJQLreVnyxbz BDHpwXMvSD9+oXGUahZeWY5yTZSyscxhajCp34/TYgTtRubJWxRfbPxKOPUhgFBkzW 1CiBts3ibuerfldCFjnGIOVJOGX77c0gADhUxmSaMPPRyePq1FhlPuifVqbeJmBLGZ KPJeEFFWyJLFRGQGaetIMEQcx3W8meqA/ji+w8ujcs18mvrk5fJjeuPgi0lsDZrv7v 0vVy1XIUiFxAA== Received: from louiss-mbp.fritz.box (unknown [217.150.232.37]) by mr85p00im-hyfv06011301.me.com (Postfix) with ESMTPSA id 00F53580F50 for ; Tue, 25 Jun 2019 17:16:12 +0000 (UTC) From: Louis Brauer Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Update materialized view definition kills indexes Date: Tue, 25 Jun 2019 19:16:12 +0200 References: <896A21F4-F534-46C9-BF11-CDE6D0DC10BC@mac.com> To: pgsql-admin@lists.postgresql.org In-Reply-To: <896A21F4-F534-46C9-BF11-CDE6D0DC10BC@mac.com> Message-Id: <8F364779-1FC9-4220-9449-B148596E3D5B@mac.com> X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-06-25_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=391 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1812120000 definitions=main-1906250130 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Sorry guys, wrong list. Apologies! > Am 25.06.2019 um 19:14 schrieb Louis Brauer : >=20 > Hi there >=20 > I=E2=80=99ve noticed that in the recent version of pgAdmin 4.8 when I = update the definition of a MATERIALIZED VIEW, the indexed will not be = recreated. >=20 > Personally I think that pgAdmin should recreate the indexes or at = least warn the user that the indexes will be gone. >=20 > What do you think? >=20 > - Louis >=20