Re: 'pg_global' cannot be used as default_tablespace. - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: 'pg_global' cannot be used as default_tablespace.
Date
Msg-id ZUO7hd9OVzhGmqFn@momjian.us
Whole thread Raw
In response to Re: 'pg_global' cannot be used as default_tablespace.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 'pg_global' cannot be used as default_tablespace.
List pgsql-docs
On Thu, Nov  2, 2023 at 09:58:54AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I found a cleaner improvement, attached.
> 
> OK by me.  Maybe that doesn't make the point strongly enough,
> but we can hope it's enough.

Agreed.  I thought last night about the sentence and realized when we
say pg_global is used for shared system catalogs, we are not saying
other object can't also be put there, so the "only" seemed required, and
once I added that, the second sentence fragment seemed unnecessary.

Plus, this report is from three years ago and I haven't seen any other
reports since then.

I also prefer manage-ag.sgml because we already talk about pg_global
there, and hopefully users of GUC tablespaces and CREATE TABLE will see
it there, or at least look for it when they get the error on creation.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-docs by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Documentation of return values of range functions lower and upper
Next
From: PG Doc comments form
Date:
Subject: Please make a note regarding the PL/pgSQL FOUND variable