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 (CV
As part of my testing, I noticed this bug. My database has a
search_path set in the database vars. It dumps lik ethis:
DROP DATABASE usa;
CREATE DATABASE usa WITH TEMPLATE = template0 OWNER = usadmin ENCODING =
'LATIN1';
ALTER DATABASE usa SET search_path TO 'public, contrib';
Notice the sing
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> Is a fix for this required for only search_path, or is it a more general
> problem?
I think this has to be driven off the GUC_LIST_INPUT and/or
GUC_LIST_QUOTE flag bits (too late at night to remember just what those
two flags do, but one or bo
