Re: Failed Assert in pgstat_assoc_relation
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: vignesh C <vignesh21@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-12-02T05:48:48Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2022-12-02 00:08:20 -0500, Tom Lane wrote: >> Just the table-to-view hack. I'm not aware that there are any other >> cases, and it seems hard to credit that there ever will be any. > I can see some halfway credible scenarios. E.g. converting a view to a > matview, or a table into a partition. I kind of wonder if it's worth keeping > the change, just in case we do - it's not that easy to hit... I'd suggest putting in an assertion that the relkind isn't changing, instead. When and if somebody makes a credible feature patch that'd require relaxing that, we can see what to do. (There's a couple of places in rewriteHandler.c that could perhaps be simplified, too.) regards, tom lane
Commits
-
Prevent pgstats from getting confused when relkind of a relation changes
- af3517c15c84 11.19 landed
- 35b99a18f5fb 12.14 landed
- 7944d2d8c78b 13.10 landed
- cb2e7ddfe571 16.0 landed
- 6344bc0974dc 14.7 landed
- c6a60471a1a5 15.2 landed
-
Remove logic for converting a table to a view.
- b23cd185fd54 16.0 landed