database then pg_dump the temp,
followed by restore of temp as though it were the whole thing?
Best,
Iavor
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 19, 2004 6:45 PM
To: Iavor Raytchev
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] import/export or
:[EMAIL PROTECTED]
Sent: Sunday, September 19, 2004 6:45 PM
To: Iavor Raytchev
Cc: [EMAIL PROTECTED]
Subject: Re: [GENERAL] import/export or moving data between databases
"Iavor Raytchev" <[EMAIL PROTECTED]> writes:
> The problem we face is -
> When we start to imp
"Iavor Raytchev" <[EMAIL PROTECTED]> writes:
> The problem we face is -
> When we start to import - the triggers are executed - which must not happen. We
> found a way to turn the triggers off for the time of import and then turn them on
> after the import. However we can turn the triggers o
Hello,
We a situation with a central database that contains the data that needs to be
presented at N off-line terminals (N can be 5 000 can be 15 000). Each terminal
presents unique data. The central database is used for data preparation. Then the data
for each terminal is exported as separate
