aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvalidate.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-01-31 15:17:15 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2025-01-31 15:17:15 -0500
commit53a49365052026907afff7613929710d1e7f0da0 (patch)
tree39a4c01fc1222431506d584506879e0099f8c6b8 /src/backend/access/gist/gistvalidate.c
parentd4c3a6b8ad830882066122081a7141ecd573f45d (diff)
downloadpostgresql-53a49365052026907afff7613929710d1e7f0da0.tar.gz
postgresql-53a49365052026907afff7613929710d1e7f0da0.zip
Doc: add commentary about cowboy assignment of maintenance_work_mem.
Whilst working on commit 041e8b95b I happened to notice that parallel_vacuum_main() assigns directly to the maintenance_work_mem GUC. This is definitely not per project conventions, so I tried to fix it to use SetConfigOption(). But that fails with "parameter cannot be set during a parallel operation". It doesn't seem worth working on a cleaner answer, at least not till we have a few more instances of similar problems. But add some commentary, just so nobody gets the idea that this is an approved way to set a GUC.
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions