Thanks for the response Tom.=20
Yes, after upgrade to 9.5, I had the hard links. But next step I migrated t=
he tables to new tablespaces , with logging. Wouldn't "alter tablespace set=
tablespace, set logged " supposed to physically recreate the tables in the=
new tablespace, and remove the space occupied by the original unlogged tab=
le?=20
=20
Example: I had an unlogged table: test_y1981, in tablespace: ts_data2, I=
executed statement like the following:
psql> alter table test_y1981 set tablespace ts_data5 , set logged;
I was expecting to see the table files in volume supporting tablespace: "ts=
_data5" ( which is what I see), but no space taken up in volume supporting =
tablespace "ts_data2". As per pg_class, there are no objects in tablespace =
"ts_land2".
Thanks
Ganesh
________________________________________
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Friday, June 3, 2016 1:05 PM
To: Ganesh Kannan
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] After upgrade to 9.5 space not being released
Ganesh Kannan <ganesh.kannan@weatheranalytics.com> writes:
> Upgraded a very large database from Pg 9.4.7 to 9.5.3 , using pg_upgrade =
--link option.
Did you ever remove the old data directory? If not, the table files are
still linked there.
regards, tom lane