Ok, thanks.
On Sun 26 Aug, 2018, 10:46 AM Paul Carlucci,
wrote:
> There's a handful of hidden columns like Xmin and Xmax per row that you're
> not accounting for, header info per page, reserve space, free space... The
> physical size on disk is reasonable.
>
> Otherwise you can reduce the number
There's a handful of hidden columns like Xmin and Xmax per row that you're
not accounting for, header info per page, reserve space, free space... The
physical size on disk is reasonable.
Otherwise you can reduce the number of rows by cleaning up and moving out
old data, reduce the width of each ro
Thank you very much for your prompt response.
Please guide me below things.
How to check rows got corrupted?
How to check table got corrupted?
How to check which row is occupied more space in the table?
Is this expected?
[image: image.png]
On Sun, 26 Aug 2018 at 09:46, Adrian Klaver
wrote:
On 08/25/2018 08:36 PM, Raghavendra Rao J S V wrote:
Hi All,
One of our database size is 50gb. Out of it one of the table has
149444622 records. Size of that table is 14GB and its indexes size is 16GB.
Total size of the table and its indexes are 30GB. I have perfomred the
below steps on that t
Hi All,
One of our database size is 50gb. Out of it one of the table has 149444622
records. Size of that table is 14GB and its indexes size is 16GB.
Total size of the table and its indexes are 30GB. I have perfomred the
below steps on that table.
reindex table table_name;
vacuum full verbose ana
