Re: Freeze avoidance of very large table. - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Freeze avoidance of very large table.
Date
Msg-id CAHGQGwH9WCS817rs=DYqw9=UbxBrZ7iyw33tqgpLgj4zP0v3aA@mail.gmail.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Freeze avoidance of very large table.  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Fri, Oct 2, 2015 at 8:14 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>> +#define Anum_pg_class_relallfrozen        12
>> Why is pg_class.relallfrozen necessary? ISTM that there is no user of it now.
>
> The relallfrozen would be useful for user to estimate time to vacuum
> freeze or anti-wrapping vacuum before being done them actually.
> (Also this value is used on regression test.)
> But this information is not used on planning like relallvisible, so it
> would be good to move this information to another system view like
> pg_stat_*_tables.

Or make pgstattuple and pgstattuple_approx report even the number
of frozen tuples?

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: ON CONFLICT issues around whole row vars,
Next
From: Takashi Ohnishi
Date:
Subject: Re: Connection string parameter 'replication' in documentation