| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: pg_stat_*_columns? |
| Date: | 2015-06-16 02:47:49 |
| Message-ID: | 557F8E55.5050702@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/8/15 3:26 PM, Joel Jacobson wrote:
> So I've heard from Magnus Hagander today IRL at our Stockholm PostgreSQL
> User Group meeting where we discussed this idea. He told me the overhead
> in the statistics collector is mainly when reading from it, not that
> much when writing to it.
I've heard enough stories of people moving the stats files to faster
storage that I'm not sure how true that really is...
> Magnus idea was to first optimize the collector to make it less of a
> problem to collect more data. Sounds like a good thing to do, but maybe
> more data in it wouldn't be a problem as long as you don't read too
> often from it?
The stats collector is a known problem under certain circumstances, so
improving it would probably be a good thing. The first thing that comes
to mind is splitting it into more files.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Kamholz | 2015-06-16 02:56:51 | Re: query execution time faster with geqo on than off: bug? |
| Previous Message | Jim Nasby | 2015-06-16 02:04:56 | Re: On columnar storage |