Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.
Дата
Msg-id 16819.1476897933@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: Move pg_largeobject to a different tablespace *without* turning on system_table_mods.  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
Bruce Momjian <bruce@momjian.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.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: incorrect libpq comment
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Portable check for unportable macro usage