| From: | Gaetano Mendola <mendola(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | pg_tables bug? |
| Date: | 2015-12-17 07:54:49 |
| Message-ID: | CAJycT5oMbH2ftXfiJmCEawa_-F5tCVe4v+6FZUHankng3TjtmA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-12-17 07:55:22 | Re: Refactoring speculative insertion with unique indexes a little |
| Previous Message | Peter Geoghegan | 2015-12-17 07:44:15 | Re: Refactoring speculative insertion with unique indexes a little |