| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dimitri Maziuk <dmaziuk(at)bmrb(dot)wisc(dot)edu> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: logical replication snapshots |
| Date: | 2018-07-25 15:28:28 |
| Message-ID: | 20180725152827.g22qmue3wgycifjh@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2018-07-24 14:02:26 -0500, Dimitri Maziuk wrote:
> On 07/24/2018 01:43 PM, Andres Freund wrote:
> > On 2018-07-24 12:22:24 -0500, Dimitri Maziuk wrote:
> >> On 07/24/2018 12:21 PM, Alvaro Herrera wrote:
> >>>
> >>> Are you serious about us trying to diagnose a bug with this description?
> >>
> >> What do you want to know, exactly?
> >
> > A recipe that we can follow and reproduce the issue.
>
> The nutshell version is as I said: I pretty much followed the manual to
> create a test publication/subscription setup and let it run for a few
> weeks. I had to increase a few limits but otherwise everything's at the
> default settings as shipped in the rpms.
Are you really expecting us to be able to reproduce the problem based on
the above description? Our test suites do setup plain replications
setups, and the problem doesn't occur there.
> If you are asking for something other than those two extremes, please
> let me know what it is and I'll be happy to try and provide it.
A command by command reproducer would be good.
> I can send you postgres config files from both nodes and the entire
> database dump -- it's all public domain. I can `zfs send` you the
> snapshot of the entire /var/lib/pgsql/10 as is, too.
Without the genesis, that's probably not as helpful, unfortunately.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Maziuk | 2018-07-25 15:40:50 | Re: logical replication snapshots |
| Previous Message | Tom Lane | 2018-07-25 15:28:12 | Re: Order in which tables are dumped |