| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_stat_*_columns? |
| Date: | 2015-06-26 22:30:07 |
| Message-ID: | 558DD26F.3030904@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/24/15 6:41 PM, Tomas Vondra wrote:
>> Were the stories (or the experience which lead to the stories) on 9.3 or
>> later? Do they have a good way to reproduce it for testing purposes?
>
> The per-db split can only improve things if there actually are multiple
> databases, and if the objects are somehow evenly distributed among them.
> If there's a single database, or if most of the objects are in a single
> database (but stored in multiple schemas, for example), it does not help
> much. So it's trivially to reproduce the previous issues.
Right, and a single large database is a pretty common scenario.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-06-26 22:35:10 | Re: UPSERT on partition |
| Previous Message | Jim Nasby | 2015-06-26 22:22:55 | Re: object_classes array is broken, again |