| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_*_columns? |
| Date: | 2015-06-20 14:20:26 |
| Message-ID: | CA+TgmoYTmtDk8xyhRR5ntz5=577-kSiLpbe_dTXLg3-VVW837Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jun 20, 2015 at 10:12 AM, Joel Jacobson <joel(at)trustly(dot)com> wrote:
> Is there any chance the project would accept a patch which adds the
> pg_stat_*_columns-feature without first optimizing the collector?
I doubt it. It's such a pain point already that massively increasing
the amount of data we need to store does not seem like a good plan.
> I guess it
> primarily depends on how much of the new code that would need to be
> rewritten, if the collector is optimized/rewritten in the future?
I don't think that's really the issue. It's more that I think it
would be the extra data would be likely to cause real pain for users.
FWIW, I tend to think that the solution here has less to do with
splitting the data up into more files and more to do with rethinking
the format.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-20 14:55:03 | Re: pg_stat_*_columns? |
| Previous Message | Paul Ramsey | 2015-06-20 14:20:16 | Extension support for postgres_fdw |