| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Logical replication in the same cluster |
| Date: | 2017-05-01 18:31:53 |
| Message-ID: | CAH2-Wzn7QhfCdLzWheJNDAjcNC9ZCd4bn=vCzrBcXdQP+DZkew@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 1, 2017 at 11:24 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Doing catalog changes in recovery is frought with problems. Essentially
> requires starting one worker per database, before allowing access.
Do you think it's worth just covering the case where you get an error,
such as a duplicate violation? I imagine that that's the much more
common case.
--
Peter Geoghegan
VMware vCenter Server
https://www.vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mikael Kjellström | 2017-05-01 18:34:32 | Re: BuildFarm client release 4.19 |
| Previous Message | Andrew Dunstan | 2017-05-01 18:25:08 | Re: BuildFarm client release 4.19 |