On Thu, 17 Dec 2015 at 15:36 Tom Lane <t...@sss.pgh.pa.us> wrote: > Gaetano Mendola <mend...@gmail.com> writes: > > I'm playing around with tablespace (postgresq 9.4) and I found out what I > > believe is a bug in pg_tables. > > Basically if you create a database in a table space X and then you > create a > > table on the database the table is created correctly on the tablespace X > ( > > I did a check on the filesystem) however if you do a select on pg_tables > > the column tablespace for that table is empty and even worst if you dump > > the DB there is no reporting about the the database or table being on > that > > tablespace. > > Even \d doesn't report that the table is in the tablespace X. > > An empty entry in that column means that the table is in the default > tablespace for the database. Which it sounds like is what you have > here. I think it's operating as designed, though you might quibble > with the decision that showing default tablespaces explicitly would > have been clutter. >
Now it's clear thank you.
