| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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-12-02 17:57:53 |
| Message-ID: | 20131202175752.GD4373@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Mon, Dec 02, 2013 at 11:41:10AM -0500, Bruce Momjian wrote:
> > > If there were databases or users with default_transaction_read_only
> > > set in the old cluster, the pg_dumpall run will cause that property
> > > to be set in the new cluster, so what you are saying seems to be
> > > that a cluster can't be upgraded to a new major release if any
> > > database within it has that set.
> >
> > That is *precisely* my use case which I initially asked about.
>
> The use-case would be that default_transaction_read_only is turned on in
> postgresql.conf
Are you telling me which use case I initially asked
about on this thread ?
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-02 17:59:41 | Re: Trust intermediate CA for client certificates |
| Previous Message | Bruce Momjian | 2013-12-02 17:44:08 | Re: Trust intermediate CA for client certificates |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-12-02 17:58:08 | Re: Draft release notes for 9.3.2 |
| Previous Message | Bruce Momjian | 2013-12-02 17:51:47 | Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block |