Re: Rethinking locking for database create/drop vs connection - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Rethinking locking for database create/drop vs connection
Date
Msg-id 44595E84.1000005@calorieking.com
Whole thread Raw
In response to Rethinking locking for database create/drop vs connection startup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> It's slightly annoying to have to read the flat file twice, but
> for reasonable numbers of databases per installation I don't think
> this will pose any material performance penalty.  The file will
> certainly still be sitting in kernel disk cache.

Dropping a db isn't exactly a "common" occurrence anyway no?



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Warts with SELECT DISTINCT
Next
From: Greg Stark
Date:
Subject: Re: Warts with SELECT DISTINCT