From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com>, "Hilbert, Sebastian" <Sebastian(dot)Hilbert(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] pg_upgrade ?deficiency |
Date: | 2013-11-23 17:24:21 |
Message-ID: | 20131123172421.GL4151@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Sat, Nov 23, 2013 at 12:11:56PM -0500, Tom Lane wrote:
> I also agree with *not* changing pg_dump, since it is not the charter
> of pg_dump to recreate a whole cluster, and the objection about possibly
> restoring into a database that was meant to be protected by this setting
> seems to have some force.
This is were the suggestion comes in (which was already raised)
to add some commandline option to the effect of
--ignore-default-tx-readonly
which, however, I agree with can be worked around by
projects (like GNUmed, in which context this issue
came up at all) providing restore scripts setting
PGOPTIONS appropriately ...
Thanks for all the work,
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Sebastian Hilbert | 2013-11-23 18:45:11 | Re: [GENERAL] pg_upgrade ?deficiency |
Previous Message | Tom Lane | 2013-11-23 17:21:15 | Re: Getting non_NULL right-side values on a non-matching join? |
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-11-23 17:37:12 | Re: Regress tests to improve the function coverage of schemacmds and user and tablespace files |
Previous Message | Tom Lane | 2013-11-23 17:11:56 | Re: [GENERAL] pg_upgrade ?deficiency |