Re: Bug in pg_restore with EventTrigger in parallel mode

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: fabriziomello@gmail.com
Cc: vignesh C <vignesh21@gmail.com>, Michael Paquier <michael@paquier.xyz>, Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2020-03-09T18:59:35Z
Lists: pgsql-hackers
=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello@gmail.com> writes:
> On Mon, Mar 9, 2020 at 12:27 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Which, TBH, makes me wonder about the validity of the original complaint
>> in this thread.  I don't mind delaying ET restore as long as we feasibly
>> can; but if you have an ET that is going to misbehave during restore,
>> you are in for pain, and it's hard to consider that that pain isn't
>> self-inflicted.

> The proposed patch solve the original complain. I was just trying to
> understand completely what you pointed out before and I agree with you.
> Thanks for the clear explanation.

OK, thanks for confirming that this solves your issue in practice.

> About the patch LGTM and IMHO we should back-patch it to all supported
> versions.

Done.

			regards, tom lane



Commits

  1. Fix pg_dump/pg_restore to restore event triggers later.