Re: moving system catalogs to another tablespace - Mailing list pgsql-hackers

From Tom Lane
Subject Re: moving system catalogs to another tablespace
Date
Msg-id 1699.1254841091@sss.pgh.pa.us
Whole thread Raw
In response to Re: moving system catalogs to another tablespace  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: moving system catalogs to another tablespace
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> I don't agree that pg_largeobject is a random catalog either -- it is,
> in fact, the only catalog in which an interesting size is to be
> expected.

Yeah, I have sometimes thought that pg_largeobject shouldn't be
considered a system catalog at all.  It's more nearly like a toast
table, ie, it's storing "out of line" user data.

This has some interesting connections with the proposed changes
for associating privilege data with large objects.  The proposed
"meta" table would certainly qualify as a system catalog still.
Would there be any sense in redefining pg_largeobject as an actual
toast table attached to that catalog?  Probably not, or at least
it wouldn't directly contribute to solving Jaime's problem.
But it seems like now would be a good time to think outside the
box a little bit about where we want to go with pg_largeobject.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Standby on git
Next
From: Jaime Casanova
Date:
Subject: Re: moving system catalogs to another tablespace