| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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:34:41 |
| Message-ID: | 20161019173441.GU5087@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 19, 2016 at 01:25:33PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Wed, Oct 19, 2016 at 09:44:05AM -0700, David G. Johnston wrote:
> >> 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?
>
> According to
> https://www.postgresql.org/message-id/200407110311.i6B3BBW24899%40candle.pha.pa.us
> it already is ;-)
>
> Personally though I'd narrow the scope to just consider pg_largeobject
> (and maybe pg_largeobject_metadata). I see no use-case for moving other
> catalogs out of the DB's default tablespace, and doing so would create a
> large space of poorly-tested opportunities for failure.
Ah, I see it now:
Allow toast tables to be moved to a different tablespace
moving toast table to its own tablespace
patch : Allow toast tables to be moved to a different tablespace
--
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 | Bruce Momjian | 2016-10-19 17:35:52 | Re: incorrect libpq comment |
| Previous Message | Andres Freund | 2016-10-19 17:32:03 | Re: Portable check for unportable <ctype.h> macro usage |