Le mar. 10 déc. 2019 à 20:48, Jeff Janes a écrit :
> On Tue, Dec 10, 2019 at 11:43 AM Guillaume Lelarge
> wrote:
>
> This query uses the column statistics to estimate bloat. AFAIK, json
>> columns don't have statistics, so the estimation can't be relied on (for
>> this specific table at least).
On Tue, Dec 10, 2019 at 11:43 AM Guillaume Lelarge
wrote:
This query uses the column statistics to estimate bloat. AFAIK, json
> columns don't have statistics, so the estimation can't be relied on (for
> this specific table at least).
>
This was true prior to 9.5 (for xml at least, I don't know
Le ven. 6 déc. 2019 à 18:18, Mike Schanne a écrit :
> Hi all,
>
>
>
> This question is somewhat related to my previous question:
>
>
> https://www.postgresql.org/message-id/0871fcf35ceb4caa8a2204ca9c38e330%40USEPRDEX1.corp.kns.com
>
>
>
> I was attempting to measure the benefit of doing a VACUUM
Yes, the additional bitmap could certainly explain the increase.
Thanks,
Mike
-Original Message-
From: Justin Pryzby [mailto:pry...@telsasoft.com]
Sent: Friday, December 06, 2019 6:29 PM
To: Mike Schanne
Cc: pgsql-performa...@postgresql.org
Subject: Re: unexpected result for wastedbytes
On Fri, Dec 06, 2019 at 05:18:20PM +, Mike Schanne wrote:
> Hi all,
>
> This question is somewhat related to my previous question:
> https://www.postgresql.org/message-id/0871fcf35ceb4caa8a2204ca9c38e330%40USEPRDEX1.corp.kns.com
>
> I was attempting to measure the benefit of doing a VACUUM