Re: Rethinking locking for database create/drop vs connection

From: Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rethinking locking for database create/drop vs connection
Date: 2006-05-04 01:53:08
Message-ID: 44595E84.1000005@calorieking.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruno Wolff III 2006-05-04 03:10:57 Re: Warts with SELECT DISTINCT
Previous Message Nikolay Samokhvalov 2006-05-03 22:00:37 Re: [SoC] Relation between project "XML improvements" and "pgxml"