Re: bug in pg_dump ALTER DATABASE - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: bug in pg_dump ALTER DATABASE
Date
Msg-id 40F3925D.5090009@familyhealth.com.au
Whole thread Raw
In response to Re: bug in pg_dump ALTER DATABASE  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-hackers
> So what are we going to do about this problem?
> 
> The pg_settings view does not have enough information to determine it 
> generically.  (It only says 'string', not 'list'...)
> 
> I propose that we modify pg_dumpall to hard-code the set of list-type 
> GUC variables for each backend version.
> 
> The current (CVS) list of such GUCs is:
> 
> * DateStyle
> * preload_libraries
> * search_path
> * log_destination
> * custom_variable_classes (probably doesn't need to be worried about)
> 
> Shall I go ahead and do this?

Oh, and we'll need to fix the pg_settings view for the future, because 
otherwise it will make life difficult for GUI writies (like me)...

Chris



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Another pg_dump bug
Next
From: "Magnus Hagander"
Date:
Subject: Re: Is "trust" really a good default?