| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "zhoushulin1992(at)gmail(dot)com" <zhoushulin1992(at)gmail(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 'pg_global' cannot be used as default_tablespace. |
| Date: | 2023-11-02 15:08:53 |
| Message-ID: | ZUO7hd9OVzhGmqFn@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Nov 2, 2023 at 09:58:54AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-11-02 16:42:19 | Please make a note regarding the PL/pgSQL FOUND variable |
| Previous Message | Laurenz Albe | 2023-11-02 14:42:53 | Re: Documentation of return values of range functions lower and upper |