Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.
Date
Msg-id 20161019171109.GT5087@momjian.us
Whole thread Raw
In response to Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Oct 19, 2016 at 09:44:05AM -0700, David G. Johnston wrote:
> On Wed, Oct 19, 2016 at 9:29 AM, Bruce Momjian <bruce@momjian.us> wrote:
> 
>     On Tue, Oct 18, 2016 at 04:51:54PM +0200, Andreas Joseph Krogh wrote:
>     >     > 2. Being able to move pg_largeobject to a different tablespace
>     >     >    *without* turning on system_table_mods. This is important for
>     >     >    people storing LOTS of large-objects on separate
>     >     >    disks (non-SSD) and hence in a different tablespace.
>    
>     I think an open question is why you would not want to move the other
>     system tables at the same time you move pg_largeobject.
> 
> 
> 
> ​I think the theory of having all system tables except LO on SSD storage, and
> having LO on a less performant device, makes sense.

OK, so is this a TODO item?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Transactions involving multiple postgres foreign servers
Next
From: Robert Haas
Date:
Subject: incorrect libpq comment