| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| 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 16:44:05 |
| Message-ID: | CAKFQuwaqhDtL56CiFiaRuSpGDi3HB0WMJvXSe-rODr3w8HzH8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-19 16:44:24 | Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods. |
| Previous Message | Bruce Momjian | 2016-10-19 16:42:11 | Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods. |