Re: pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace
Date: 2016-10-09 21:43:23
Message-ID: CA+TgmoYECizNd8MAwr6aGzRSG7P6p7c1sgt71LbSMZZOc+pT=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 8, 2016 at 9:02 AM, Andreas Joseph Krogh <andreas(at)visena(dot)com>
wrote:

> (I've set allow_system_table_mods=on in postgresql.conf)
>

Any configuration that includes this step is considered unsupported by the
PostgreSQL community.

It might be a good idea if we supported storing large objects in an
alternate tablespace, or in multiple tables in the same or different
tablespaces. However, if you can only get there by enabling
allow_system_table_mods, then we don't.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-10-09 22:10:33 Re: Relids in upper relations
Previous Message Tomas Vondra 2016-10-09 20:47:21 Re: Speed up Clog Access by increasing CLOG buffers