| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, "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-22 21:55:10 |
| Message-ID: | 1385157310.96336.YahooMailNeo@web162904.mail.bf1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
This covers pg_dumpall globals. Tested with a read-only postgres
database and with default_transaction_read_only = on in the
postgresql.conf file.
It does nothing about pg_upgrade, which is sort of a separate
issue. My inclination is that connections to the new cluster
should set this and connections to the old should not.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| pg_dump-vs-default_transaction_read_only-v2.diff | text/x-diff | 1.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-22 21:58:24 | Re: [GENERAL] pg_upgrade ?deficiency |
| Previous Message | Andres Freund | 2013-11-22 21:52:53 | Re: [GENERAL] pg_upgrade ?deficiency |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-22 21:58:24 | Re: [GENERAL] pg_upgrade ?deficiency |
| Previous Message | Andres Freund | 2013-11-22 21:52:53 | Re: [GENERAL] pg_upgrade ?deficiency |