Re: bug in pg_dump ALTER DATABASE

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug in pg_dump ALTER DATABASE
Date: 2004-07-13 07:42:21
Message-ID: 40F3925D.5090009@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2004-07-13 07:43:18 Re: Is "trust" really a good default?
Previous Message Christopher Kings-Lynne 2004-07-13 07:33:08 Another pg_dump bug