Skip site navigation (1) Skip section navigation (2)

Re: TODO item: Allow more complex user/database default GUC settings

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>,Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>,Bernd Helmle <mailings(at)oopsware(dot)de>,Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO item: Allow more complex user/database default GUC settings
Date: 2009-09-30 21:01:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane escribió:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > FWIW I came up with a preliminary patch for a new psql command \dus that
> > shows settings.  It takes a pattern that's used to constrain on roles.
> > Thus there is no way to view settings for a database.  If there's a need
> > for that we could use another command, say \dls.
> Why not two pattern arguments?
> 	\drds [ role-pattern [ db-pattern ]]

Hmm, interesting idea, patch attached.  This required changing the API
of processSQLNamePattern to return a bool indicating whether a clause
was added; otherwise, when processing the second pattern it was
impossible to figure out if we needed a WHERE or not.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

Attachment: settings-psql-2.patch
Description: text/x-diff (6.1 KB)

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-09-30 21:05:35
Subject: Re: latest hstore patch
Previous:From: Tom LaneDate: 2009-09-30 20:52:48
Subject: Re: CommitFest 2009-09, two weeks on

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group