| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org>, pgsql-general(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: Megabytes of stats saved after every connection |
| Date: | 2005-07-28 18:28:04 |
| Message-ID: | 25889.1122575284@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> On 7/28/2005 2:03 PM, Tom Lane wrote:
>> Well, there's the problem --- the stats subsystem is designed in a way
>> that makes it rewrite its entire stats collection on every update.
>> That's clearly not going to scale well to a large number of tables.
>> Offhand I don't see an easy solution ... Jan, any ideas?
> PostgreSQL itself doesn't work too well with tens of thousands of
> tables.
Really? AFAIK it should be pretty OK, assuming you are on a filesystem
that doesn't choke with tens of thousands of entries in a directory.
I think we should put down a TODO item to see if we can improve the
stats subsystem's performance in such cases.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2005-07-28 18:29:57 | Re: GUID for postgreSQL |
| Previous Message | Jan Wieck | 2005-07-28 18:20:04 | Re: Megabytes of stats saved after every connection |