| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Mathis Rudolf <mathis(dot)rudolf(at)credativ(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Alias collision in `refresh materialized view concurrently` |
| Date: | 2021-06-02 00:30:55 |
| Message-ID: | CA+hUKGK=TgR3hefhjzsVGZzXQ+A2TtgekFtQ3aGEso82LJab5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 2, 2021 at 2:02 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> PSA v3 patch. I added a commit message and made some cosmetic adjustments.
Reminds me of this fun topic in Lisp:
https://en.wikipedia.org/wiki/Hygienic_macro#Strategies_used_in_languages_that_lack_hygienic_macros
I wondered if we could find a way to make identifiers that regular
queries are prohibited from using, at least by documentation. You
could take advantage of the various constraints on unquoted
identifiers in the standard (for example, something involving $), but
it does seem a shame to remove the ability for users to put absolutely
anything except NUL in quoted identifiers. I do wonder if at least
using something like _$mv would be slightly more principled than
pg_mv_1234, since nothing says pg_XXX is reserved (except in some very
specific places like schema names), and the number on the end seems a
bit cargo-cultish.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-06-02 01:03:38 | Re: Alias collision in `refresh materialized view concurrently` |
| Previous Message | Tom Lane | 2021-06-02 00:04:27 | Re: CALL versus procedures with output-only arguments |