BUG #7874: GUC's not in database dumps

The following bug has been logged on the website:

Bug reference:      7874
Logged by:          Joe Van Dyk
Email address:      joe@tanga.com
PostgreSQL version: 9.2.1
Operating system:   OSX, Linux
Description:        =


If I run:
   alter database foo set my.name =3D 'joe';

that GUC isn't available inside backups of that database.

It does show up when doing "pg_dumpall -s". =


It does *not* show up when doing "pg_dumpall -g"


$ createdb foo
$ psql foo
psql (9.2.1)

foo=3D# alter database foo set my.name =3D 'joe';
ALTER DATABASE

foo=3D# \q

$ pg_dump foo > foo.sql

$ cat foo.sql
--
-- PostgreSQL database dump
--

SET statement_timeout =3D 0;
SET client_encoding =3D 'UTF8';
SET standard_conforming_strings =3D on;
SET check_function_bodies =3D false;
SET client_min_messages =3D warning;

--
-- Name: plpgsql; Type: EXTENSION; Schema: -; Owner: =

--

CREATE EXTENSION IF NOT EXISTS plpgsql WITH SCHEMA pg_catalog;

--
-- Name: EXTENSION plpgsql; Type: COMMENT; Schema: -; Owner: =

--

COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural language';

--
-- Name: public; Type: ACL; Schema: -; Owner: joe
--

REVOKE ALL ON SCHEMA public FROM PUBLIC;
REVOKE ALL ON SCHEMA public FROM joe;
GRANT ALL ON SCHEMA public TO joe;
GRANT ALL ON SCHEMA public TO PUBLIC;

--
-- PostgreSQL database dump complete
--