ver
Sent: Thursday, February 13, 2020 6:21 PM
To: Jason Ralph ; Michael Lewis
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_upgrade —link does it remove table bloat
On 2/13/20 12:45 PM, Jason Ralph wrote:
> @Adrian Klaver,
> I was concerned with the 1.4 value of tbloat and wastedby
On 2/13/20 12:45 PM, Jason Ralph wrote:
@Adrian Klaver,
I was concerned with the 1.4 value of tbloat and wastedbytes value, then again
the last autovacuum was at 2020-02-13 02:25:22.533372-05 and I took this
snapshot at 3:44PMEST. So it may be ok, what do you think?
What is your concern, sto
om: Adrian Klaver
Sent: Thursday, February 13, 2020 3:19 PM
To: Jason Ralph ; Michael Lewis
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_upgrade —link does it remove table bloat
On 2/13/20 11:07 AM, Jason Ralph wrote:
> >There is more than one type of statistics though. Stats on th
Jason Ralph ;
pgsql-general@lists.postgresql.org
*Subject:* Re: pg_upgrade —link does it remove table bloat
There is more than one type of statistics though. Stats on the
distribution of data is easily recreated with analyze table_name or
analyzing the whole database. What about the stats on how m
/wiki/Show_database_bloat it still shows bloat.
Thinking it may be left over from before the pg_upgrade and auto vacuum tuning.
Best,
Jason Ralph
From: Michael Lewis
Sent: Thursday, February 13, 2020 1:02 PM
To: Adrian Klaver
Cc: Jason Ralph ;
pgsql-general@lists.postgresql.org
Subject:
On 2/13/20 10:04 AM, Jason Ralph wrote:
Well table bloat and table statistics are two different things. Bloat is the
accumulation of dead or potentially dead tuples whose space has not been marked
> as available for reuse by VACUUM or whose space has been returned to the OS
with VACUUM FULL.
mp / pg_restore since
it’s a hard link to the previous data location. Pg_upgrade with link will not
recreate the table.
Jason Ralph
-Original Message-
From: Adrian Klaver
Sent: Thursday, February 13, 2020 10:46 AM
To: Jason Ralph ;
pgsql-general@lists.postgresql.org
Subject: Re: pg_upg
There is more than one type of statistics though. Stats on the distribution
of data is easily recreated with analyze table_name or analyzing the whole
database. What about the stats on how many rows have been inserted or
updated since the last (auto)vacuum and that will be used to trigger
autovacuu
On 2/13/20 4:31 AM, Jason Ralph wrote:
When using the pg_upgrade link method to upgrade Postgres a major
version. Let’s say 9.3 to 11.6 on Centos Linux. Will table bloat carry
over to the new version. I know using —link will use hard link pointers
to the new data. So I assume all table bloat wi
