Re: Relpartbound, toasting and pg_class

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Relpartbound, toasting and pg_class
Date: 2017-06-12 21:10:28
Message-ID: a0a0cc39-644b-9e0a-dd1a-f5fdefad8f06@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/12/17 15:38, Andres Freund wrote:
> 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 */
> #endif
>
> 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...

Cases where relacl became too large have been known to exist. I'm not
sure whether relpartbound can really be that large to change the
scenario significantly.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ants Aasma 2017-06-12 21:11:35 Re: WIP: Data at rest encryption
Previous Message Andres Freund 2017-06-12 21:02:21 Re: Transactional sequence stuff breaks pg_upgrade