| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: integration bloat tables (indexes) to core |
| Date: | 2016-06-13 17:03:19 |
| Message-ID: | CAFj8pRB0DfGk2pSSg73EojqZWjGfmwQd+fipvyHjssQjTv4ijA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-06-13 18:52 GMT+02:00 Robert Haas <robertmhaas(at)gmail(dot)com>:
> On Mon, Jun 13, 2016 at 3:23 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > There are lot of useful queries (views), that are on our wiki. Some
> queries
> > are necessary for maintenance, and I am thinking these queries should be
> > integrated part of Postgres.
> >
> > Mainly queries for detecting table bloat, index bloat, But some queries
> over
> > pg_locks should be useful too.
> >
> > Notes, comments?
>
> It's likely to be hard to get agreement on which things to include.
> But if we can, it might be worth doing. It would be nice to do it as
> an extension.
>
maybe estimated pgstattuple functions ?
but bloating is too important, so I would to see solution in core more.
Regards
Pavel
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-13 17:06:37 | Re: ERROR: ORDER/GROUP BY expression not found in targetlist |
| Previous Message | Robert Haas | 2016-06-13 16:52:38 | Re: proposal: integration bloat tables (indexes) to core |