| From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
|---|---|
| To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org>, martin(dot)french(at)romaxtech(dot)com, keith(at)omniti(dot)com |
| Subject: | Re: How can I tell if pg_restore is running? |
| Date: | 2014-06-11 18:18:36 |
| Message-ID: | CAJ4CxLnDKsjKfA_6vfQkBzw3FGZwoMWy8cWnqMcS_zJ5NW_Q7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 10, 2014 at 10:57 AM, Francisco Olarte <folarte(at)peoplecall(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vasudevan, Ramya | 2014-06-11 18:24:01 | max_connections reached in postgres 9.3.3 |
| Previous Message | Steve Crawford | 2014-06-11 18:14:41 | unknown type name ‘pg_int64’ |