On Thu, Aug 6, 2020 at 9:19 PM Robert Haas <robertmh...@gmail.com> wrote: > > On Thu, Aug 6, 2020 at 2:11 AM Ashutosh Sharma <ashu.coe...@gmail.com> wrote: > > Okay, If you want I can remove the restriction on a toast table, but, > > then that means a user can directly remove the data chunks from the > > toast table without changing anything in the main table. This means we > > won't be able to query the main table as it will fail with an error > > like "ERROR: unexpected chunk number ...". So, we will have to find > > some way to identify the pointer to the chunks that got deleted from > > the toast table and remove that pointer from the main table. We also > > need to make sure that before we remove a tuple (pointer) from the > > main table, we identify all the remaining data chunks pointed by this > > tuple and remove them completely only then that table would be > > considered to be in a good state. Now, I am not sure if we can > > currently do all these things. > > That's the user's problem. If they don't have a plan for that, they > shouldn't use this tool. I don't think we can or should try to handle > it in this code. >
Okay, thanks. -- With Regards, Ashutosh Sharma EnterpriseDB:http://www.enterprisedb.com
