Re: generating catcache control data

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generating catcache control data
Date: 2019-10-10 19:55:32
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

... BTW, one other issue with changing this, at least if we want to
precompute tupdescs for all system catalogs used in catcaches, is that
that would put a very big crimp in doing runtime changes to catalogs.
While we'll probably never support changes in the physical layouts
of catalog rows, there is interest in being able to change some
auxiliary pg_attribute fields, e.g. attstattarget [1]. So we'd need
to be sure that the compiled-in tupdescs are only used to disassemble
catalog tuples, and not for other purposes.

Of course this issue arises already for the bootstrap catalogs, so
maybe it's been dealt with sufficiently. But it's something to keep
an eye on.

regards, tom lane


In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-10-10 20:14:20 Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Previous Message Daniel Wood 2019-10-10 19:48:18 BTP_DELETED leaf still in tree