diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-11-03 11:48:23 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-11-03 11:48:23 -0400 |
| commit | 3f9fe9b76f908e7ebf697c6b96f39601b6f803f3 (patch) | |
| tree | 84af2397494e37704fd0c1b28b7879f38312dc02 /src/backend/utils/adt/arrayfuncs.c | |
| parent | 272db03bb9d5fbf55cfe39776973dae72cb4bec7 (diff) | |
| download | postgresql-3f9fe9b76f908e7ebf697c6b96f39601b6f803f3.tar.gz postgresql-3f9fe9b76f908e7ebf697c6b96f39601b6f803f3.zip | |
Doc: update CREATE RULE ref page's hoary discussion of views.
This text left one with the impression that an ON SELECT rule could
be attached to a plain table, which has not been true since commit
264c06820 (meaning the text was already misleading when written,
evidently by me in 96bd67f61). However, it didn't get really bad
until b23cd185f removed the convert-a-table-to-a-view logic, which
had made it possible for scripts that thought they were attaching
ON SELECTs to tables to still work.
Rewrite into a form that makes it clear that an ON SELECT rule
is better regarded as an implementation detail of a view.
Pre-v16, point out that adding ON SELECT to a table actually
converts it to a view.
Per bug #18178 from Joshua Uyehara. Back-patch to all supported
branches.
Discussion: https://postgr.es/m/18178-05534d7064044d2d@postgresql.org
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions