pg_tables bug? - Mailing list pgsql-hackers

From Gaetano Mendola
Subject pg_tables bug?
Date
Msg-id CAJycT5oMbH2ftXfiJmCEawa_-F5tCVe4v+6FZUHankng3TjtmA@mail.gmail.com
Whole thread Raw
Responses Re: pg_tables bug?  (Michael Paquier <michael.paquier@gmail.com>)
Re: pg_tables bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<div dir="ltr">I'm playing around with tablespace (postgresq 9.4) and I found out what I believe is a bug in
pg_tables.<br/>Basically if you create a database in a table space X and then you create a table on the database the
tableis created correctly on the tablespace X ( I did a check on the filesystem) however if you do a select on
pg_tablesthe column tablespace for that table is empty and even worst if you dump the DB there is no reporting about
thethe database or table being on that tablespace.<br />Even \d doesn't report that the table is in the tablespace
X.<br/><br />Regards</div> 

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Refactoring speculative insertion with unique indexes a little
Next
From: Peter Geoghegan
Date:
Subject: Re: Refactoring speculative insertion with unique indexes a little