Horton

Re: Alias collision in `refresh materialized view concurrently`

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Bernd Helmle <mailings@oopsware.de>, Mathis Rudolf <mathis.rudolf@credativ.de>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-06-03T06:56:25Z
Lists: pgsql-hackers 
On Wed, Jun 02, 2021 at 03:44:45PM +0530, Bharath Rupireddy wrote:
> Thanks.The changes with that approach are very minimal. PSA v5 and let
> me know if any more changes are needed.

Simple enough, so applied and back-patched.  It took 8 years for 
somebody to complain about the current aliases, so that should be
enough to get us close to zero conflicts now.  I have looked a bit to
see if anybody would use this naming convention, but could not find a
trace, FWIW.
--
Michael

Commits

  1. Really fix the ambiguity in REFRESH MATERIALIZED VIEW CONCURRENTLY.

  2. Reduce risks of conflicts in internal queries of REFRESH MATVIEW CONCURRENTLY