| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Andreas Joseph Krogh <andreas(at)visena(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods. |
| Date: | 2016-10-19 17:11:09 |
| Message-ID: | 20161019171109.GT5087@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)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(at)momjian(dot)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 +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-10-19 17:16:28 | incorrect libpq comment |
| Previous Message | Bruce Momjian | 2016-10-19 17:08:42 | Re: Transactions involving multiple postgres foreign servers |