| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, "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-01 22:32:37 |
| Message-ID: | 2878751.1698877957@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Wednesday, November 1, 2023, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Did you want an error from the SET command?
> That would probably be a decent addition but the request was for us to add
> “it is not permissible to specify the pg_global tablespace for either
> default_tablespace or temp_tablespace”. In the tablespace section per the
> request but maybe also within the settings definition section.
But it *is* permissible, unless we add code to reject it during
SET as Bruce mentioned. Which seems fairly pointless to me. It's not
like there is anything unclear about the CREATE TABLE error message.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-11-01 22:35:22 | Re: Typo in "43.9.1. Reporting Errors and Messages"? |
| Previous Message | David G. Johnston | 2023-11-01 22:26:49 | Re: 'pg_global' cannot be used as default_tablespace. |