Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace
Date
Msg-id CA+TgmoYECizNd8MAwr6aGzRSG7P6p7c1sgt71LbSMZZOc+pT=g@mail.gmail.com
Whole thread Raw
In response to pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace  (Andreas Joseph Krogh <andreas@visena.com>)
Responses Re: pg_upgrade 9.5 -> 9.6 fails when pg_largeobject is in separate tablespace  (Andreas Joseph Krogh <andreas@visena.com>)
List pgsql-hackers
Tree view
On Sat, Oct 8, 2016 at 9:02 AM, Andreas Joseph Krogh <andreas@visena.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

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers
Next
From: Robert Haas
Date:
Subject: Re: Relids in upper relations