Re: 'pg_global' cannot be used as default_tablespace.

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: 'pg_global' cannot be used as default_tablespace.
Дата
Msg-id ZVJ-003PHyJm0wUo@momjian.us
обсуждение исходный текст
Ответ на Re: 'pg_global' cannot be used as default_tablespace.  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-docs
On Thu, Nov  2, 2023 at 11:08:53AM -0400, Bruce Momjian wrote:
> 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.

Patch applied to master.

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

  Only you can decide what is important to you.



В списке pgsql-docs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: T is a mandatory date time separator in RFC3339 but documentation states differently
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Documentation of return values of range functions lower and upper