Re: pg_tables bug? - Mailing list pgsql-hackers

From Gaetano Mendola
Subject Re: pg_tables bug?
Date
Msg-id CAJycT5pGHrmUP=_2nR+zwFGTCj0piPyoWTiGdxGKisVsqKQZkg@mail.gmail.com
Whole thread Raw
In response to Re: pg_tables bug?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers


On Sat, Dec 19, 2015, 01:50 Andrew Dunstan <andrew@dunslane.net> wrote:




On 12/18/2015 05:18 PM, Gaetano Mendola wrote:
> From documentation about "CREATE DATABASE name WITH TABLESAPCE =
> tablespace_name":
>
> tablespace_name
> The name of the tablespace that will be associated with the new
> database, or DEFAULT to
> use the template database's tablespace. This tablespace will be the
> default tablespace used
> for objects created in this database. See CREATE TABLESPACE for more
> information.
>
> I'm sure that my tables are created in the name space but those are
> not reported either in
> pg_tables, either in pg_dump or by \d.

1. Please don't top-post on the PostgreSQL lists. See
<http://idallen.com/topposting.html>

2. The system is working as designed and as documented - see the
comments in the docs on pg_tables. If nothing is shown for the table's
tablespace then it will be in the default tablespace for the database.
That's what you're seeing. You appear to be assuming incorrectly that it
means that the table will be in the system's default tablespace. 

I did a reply using a not correctly setup client sorry for it. I'm not new to this list. I understood now how it works. Having many database and many tablespace is a nightmare this way. I will make my own view to fix the annoyance. 

pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: Re: [sqlsmith] Failing assertions in spgtextproc.c
Next
From: Michael Paquier
Date:
Subject: Re: Making tab-complete.c easier to maintain