Re: BUG #15901: Tablespace showing as null in psql and pgadmin

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #15901: Tablespace showing as null in psql and pgadmin
Дата
Msg-id 21982.1562683195@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #15901: Tablespace showing as null in psql and pgadmin  (PG Bug reporting form <noreply@postgresql.org>)
Ответы Re: BUG #15901: Tablespace showing as null in psql and pgadmin  (Ishan joshi <ishanjoshi@live.com>)
Список pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> As I have created separate tablespace (Not using default tablespace
> pg_default or pg_global) for my new database. I have tried to create tables
> with and without tablespace parameter and both these tables while checking
> in pg_table, tablespace column showing as null. I tried to extract from
> other tables but getting tablespace as null only.

The case you showed isn't a bug: creating a table that's specified to be
in the database's default tablespace is treated the same as not specifying
any tablespace.  This is because if you change the database's default
tablespace later, such a table will be moved along with every other table
that's in the database's default tablespace.

            regards, tom lane



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: BUG #15900: `executor could not find named tuplestore` intriggers with transition table and row locks
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #15900: `executor could not find named tuplestore` in triggers with transition table and row locks