On 7/24/25 16:59, sivapostg...@yahoo.com wrote:
1. Testcase. Created a new database, modified the triggers (split into
three), populated required master data, lookup tables. Then transferred
86420 records. Checked whether all the 86420 records inserted in table1
and also whether the trigger
On Thu, Jul 24, 2025 at 8:00 PM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
[snip]
> 3. Regarding moving the logic to procedure. Won't the trigger work?
> Will it be a burden for 86420 records? It's working, if we insert few
> thousand records. After split of trigger function, it's
1. Testcase. Created a new database, modified the triggers (split into
three), populated required master data, lookup tables. Then transferred 86420
records. Checked whether all the 86420 records inserted in table1 and also
whether the trigger created the required records in table2. Yes, i
Those two columns have null values when the color turns into Red.
And the status column shows 'active' only. All those three column values are
same (null, null, active) even after 2 hours!
It works when I split the trigger function into three, one each for insert,
delete and update call from t
You might also consider Backup/Restore. It appears you're not concerned
with data being inserted into the source table after the backup is
complete? If so, you can then easily sync the two post restore.
On Wed, Jul 23, 2025 at 6:55 AM sivapostg...@yahoo.com <
sivapostg...@yahoo.com> wrote:
> Th
On 7/24/25 05:18, sivapostg...@yahoo.com wrote:
Thanks Merlin, adrain, Laurenz
As a testcase, I split the trigger function into three, one each for
insert, update, delete, each called from a separate trigger.
IT WORKS!.
It worked before, it just slowed down as your cases got bigger. You nee
Thanks Merlin, adrain, Laurenz
As a testcase, I split the trigger function into three, one each for insert,
update, delete, each called from a separate trigger.
IT WORKS!.
Shouldn't we have one trigger function for all the three trigger events? Is it
prohibited for bulk insert like this?
I tr
On Wed, Jul 23, 2025 at 2:51 AM sivapostg...@yahoo.com
wrote:
>
> Tried in PostgreSQL 11.11 , PostgreSQL 15.2 in Windows 10
>
> Here we try to transfer data from one database to another (remote) database.
>
> Tables do have records ranging from 85000 to 360 along with smaller sized
> tables.
On 7/23/25 01:50, sivapostg...@yahoo.com wrote:
Tried in PostgreSQL 11.11 , PostgreSQL 15.2 in Windows 10
The above command succeeds, when
1. The trigger in Table1 is disabled with all other constraints on.
2. The no. of rows is within 16000 or less, with Trigger enabled. We
haven't tried
On Wed, 2025-07-23 at 11:55 +, sivapostg...@yahoo.com wrote:
> 1. I tried running Copy From command from PGAdmin.
> 2. I ran pg_stat_activity also in another tab [ PGAdmin ].
>
> What I observed,
> 1. In about 2 min, in the Dashboard of PGAdmin, the colour changed to Orange
> for that pa
Thanks Laurenz Albe,
1. I tried running Copy From command from PGAdmin. 2. I ran pg_stat_activity
also in another tab [ PGAdmin ].
What I observed,1. In about 2 min, in the Dashboard of PGAdmin, the colour
changed to Orange for that particular pid.2. After few seconds, the colour
again cha
On Wed, 2025-07-23 at 08:50 +, sivapostg...@yahoo.com wrote:
> Tried in PostgreSQL 11.11 , PostgreSQL 15.2 in Windows 10
Both of these choices are unsavory. Don't use the unsupported v11,
and use 15.13 with v15.
> Here we try to transfer data from one database to another (remote) database.
Tried in PostgreSQL 11.11 , PostgreSQL 15.2 in Windows 10
Here we try to transfer data from one database to another (remote) database.
Tables do have records ranging from 85000 to 360 along with smaller sized
tables.
No issues while transferring smaller sized tables.
I here take one particula
13 matches
Mail list logo
