Re: Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patch to make...)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Time to read pg_hba.conf (Re: [PATCHES] [PATCH] Patch to make...)
Date: 2001-07-10 21:42:37
Message-ID: 11630.994801357@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> So we're looking at a possible 12% win.

Many thanks for doing this legwork.

The possible win from not having to read the file at all is probably
somewhat higher than that, but not vastly higher. Accordingly, I'd
say that pre-parsing the file is not worth the development time needed
to make it happen. However, moving the comments out is clearly worth
the (very small) amount of effort needed to make that happen. Any
objections?

> Btw., in case someone wants to go optimizing, more than 75% of the backend
> startup time is spent in InitPostgres():

No surprise, that's where all the initial database access happens. We'd
need to break it down more to learn anything useful, but I'd bet that
the initial loading of required catalog cache entries is a big chunk.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-07-10 21:47:23 Re: SOMAXCONN (was Re: Solaris source code)
Previous Message Bruce Momjian 2001-07-10 21:38:51 Re: timestamp with/without time zone

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2001-07-10 23:17:05 Re: 2 gig file size limit
Previous Message Ned Wolpert 2001-07-10 20:21:47 RE: Re: Shutdown hook imp