Re: collations in shared catalogs? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: collations in shared catalogs?
Date
Msg-id CA+TgmobcJL90CawAWOEBjR_JDK8_fWkg+22LD1kTXQkj_jqm9w@mail.gmail.com
Whole thread Raw
In response to Re: collations in shared catalogs?  (David Steele <david@pgmasters.net>)
Responses Re: collations in shared catalogs?  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Wed, Feb 25, 2015 at 7:54 PM, David Steele <david@pgmasters.net> wrote:
> +1 on 128/256 character names.
>
>> /me runs and hides.
>
> /stands brazenly in the open and volunteers to try it if I don't get
> clobbered within seconds.

I think the question is whether making lots of rows in system catalogs
better is going to have undesirable effects on (a) the size of our
initial on-disk format (i.e. how big an empty database is), (b) the
amount of memory consumed by the syscache and relcaches on workloads
that touch lots of tables/functions/whatever, or (c) CPU consumption
mostly as a result of more cache line accesses for the same operation.
If you can prove those effects are minimal, that'd be a good place to
start.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Question about lazy_space_alloc() / linux over-commit
Next
From: Andres Freund
Date:
Subject: Re: Bootstrap DATA is a pita