If you can't use a wrapper script and you can't use that flag, I'm not sure how you're going to manage to keep this a process that's simple for a typical end user to manage. From what I know, there's nothing internally on the data loading process that pg_restore uses that would guarantee you that what is loading the data is pg_restore. Might need to rethink your strategy here.
On Wed, Jun 11, 2014 at 2:18 PM, Moshe Jacobson <mo...@neadwerx.com> wrote: > > On Tue, Jun 10, 2014 at 10:57 AM, Francisco Olarte <fola...@peoplecall.com > > wrote: > >> Is there any reason to avoid pg_restore --disable-triggers ? > > > Yes, this extension needs to work with everyone's normal restore process. > Otherwise I would have to ask everyone who used my extension to modify > their pg_restore command. > > This also means that I can't rely on a wrapper to pg_restore, as Keith > suggested earlier. > > > > Moshe Jacobson > Manager of Systems Engineering, Nead Werx Inc. <http://www.neadwerx.com> > 2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339 > > "Quality is not an act, it is a habit." -- Aristotle >
