Re: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc. - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.
Date
Msg-id d7d168cb94fb5543fd603a4deb79e4a253a5725a.camel@j-davis.com
Whole thread
In response to CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.  (Noah Misch <noah@leadboat.com>)
Responses RE: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.
Re: CREATE SUBSCRIPTION ... SERVER vs. pg_dump, etc.
List pgsql-hackers
On Mon, 2026-08-03 at 16:06 +0530, Amit Kapila wrote:
> Right, that is possible. In such a scenario, the current behavior of
> the apply-worker appears okay to me. Anyway, the feature
> disable_on_error is for the user to evaluate/analyze the current
> ERROR
> and accordingly take the next action. In this case, she can enable
> the
> subscription again.

That makes sense to me.

> > Or, perhaps these are just edge cases, and part (b) is not very
> > important?
> >
>
> I think so. We don't need to do anything for part (b).

Agreed.

> BTW, shall we add a detailed comment as to why we separate the load
> of
> connection info from other subscription parameters for future readers
> on the following lines:

Done using your wording in v4-0001.

New v4 series attached.

Regards,
    Jeff Davis


Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Add a hook for handling logical decoding messages on subscribers.
Next
From: Fujii Masao
Date:
Subject: Re: data_checksums + debug_discard_caches = crash