Just noticed that pg_class now has several varlena fields:
#ifdef CATALOG_VARLEN                   /* variable-length fields start here */
        /* NOTE: These fields are not present in a relcache entry's rd_rel 
field. */
        aclitem         relacl[1];              /* access permissions */
        text            reloptions[1];  /* access-method-specific options */
        pg_node_tree relpartbound;      /* partition bound node tree */

of those relpartbound is fairly new. And pretty much unbounded in
size. Aren't we going to run into issues because pg_class doesn't have a
toast table? It's quite reasonable to use a multi-field composite type
as a partition boundary...


Andres Freund

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to