From: Duncan Sands <duncan.sands@deepbluecap.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: pg_restore with --disable-triggers discards ENABLE ALWAYS
Date: Fri, 13 Sep 2024 11:08:16 +0200
Message-ID: <89aae487-4168-406d-a5e5-2f0c790634e6@deepbluecap.com> (raw)
In-Reply-To: <4156698.1726174027@sss.pgh.pa.us>
References: <d374b6fc-4217-48a9-8639-2c9b4d3a92d0@deepbluecap.com>
<78a13f951a03bf325027f8dcfb32b1b5089cdb14.camel@cybertec.at>
<4156698.1726174027@sss.pgh.pa.us>
Hi Tom, I accidentally sent my previous reply without completing it. Here's the
rest: Your suggestion as to the root cause certainly sounds plausible. If
no-one has the energy to fix it, maybe it's best to at least add a note about
this in the pg_restore --disable-triggers documentation.
Best wishes, Duncan.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: duncan.sands@deepbluecap.com, tgl@sss.pgh.pa.us, laurenz.albe@cybertec.at, pgsql-bugs@lists.postgresql.org
Subject: Re: pg_restore with --disable-triggers discards ENABLE ALWAYS
In-Reply-To: <89aae487-4168-406d-a5e5-2f0c790634e6@deepbluecap.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox