| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Remaining beta blockers |
| Date: | 2013-05-03 16:15:27 |
| Message-ID: | 20130503161526.GF2467@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian escribió:
> On Fri, May 3, 2013 at 05:24:54PM +0200, Andres Freund wrote:
> > The problem with an extra metadata fork is that it essentially would
> > double the files in a cluster and it would also noticeably increase the
> > amount of open files we need.
> > There have been quite some complaints about CREATE DATABASE speed, I
> > am not sure we want to make it even slower :(
>
> Agreed. We start to get into file system performance issues at that
> point. I have often wondered if we need to create hash the files into
> subdirectories for databases with many tables. Has anyone profiled
> this?
Modern filesystems use trees to store file nowadays, not linear arrays,
and so that old scenario (long time to find one specific directory entry
within a directory containing lots of files) is no longer that serious a
problem.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-05-03 16:19:27 | Re: Remaining beta blockers |
| Previous Message | Tom Lane | 2013-05-03 16:10:14 | Re: Remaining beta blockers |