Re: TODO item: Allow more complex user/database default GUC settings - Mailing list pgsql-hackers

From decibel
Subject Re: TODO item: Allow more complex user/database default GUC settings
Date
Msg-id CC66F887-4067-4745-97B5-48F7E2B168AC@decibel.org
Whole thread Raw
In response to Re: TODO item: Allow more complex user/database default GUC settings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sep 27, 2009, at 9:19 PM, Tom Lane wrote:
> What we seem to be lacking in this case is a good tech-speak
> option for the underlying catalog name.  I'm still not happy
> with having a catalog and a view that are exactly the same
> except for "s", especially since as Alvaro notes that won't
> lead to desirable tab-completion behavior.  OTOH, we have
> survived with pg_index vs pg_indexes, so maybe it wouldn't
> kill us.


Another option is to revisit the set of system views (http:// 
pgfoundry.org/projects/newsysviews/). IIRC there was some other  
recent reason we wanted to do that.
-- 
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828




pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: TODO item: Allow more complex user/database default GUC settings
Next
From: Josh Berkus
Date:
Subject: Re: Rejecting weak passwords