| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Postgresql General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: 9.2 upgrade glitch with search_path |
| Date: | 2013-01-15 21:32:48 |
| Message-ID: | 3411.1358285568@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sun, Jan 13, 2013 at 04:51:55PM -0500, Tom Lane wrote:
>> pg_dump does not dump/restore database properties, only database
>> contents. Properties are the responsibility of pg_dumpall, which
>> you bypassed (for databases anyway).
> Isn't this a bug? Seems there is no way to get these exported without
> pg_dumpall non-'g' mode.
No, it's not a bug. It is something that'd be nice to make more
flexible, but "bug" is an inappropriate pejorative. (If you are
unsure about the dividing line, ask yourself if we'd back-patch
such a change.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-15 22:30:18 | Re: [SQL] Curious problem of using BETWEEN with start and end being the same versus EQUALS '=' |
| Previous Message | Chris Angelico | 2013-01-15 21:10:26 | Re: plpython intermittent ImportErrors |