Re: Minimal logical decoding on standbys

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, fabriziomello(at)gmail(dot)com, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, "[pgdg] Robert Haas" <robertmhaas(at)gmail(dot)com>, Rahila Syed <rahila(dot)syed(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Minimal logical decoding on standbys
Date: 2021-08-26 11:35:18
Message-ID: 47606911-cf44-5a62-21d5-366d3bc6e445@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I noticed the tests added in this patch set are very slow. Here are
some of the timings:

...
[13:26:59] t/018_wal_optimize.pl ................ ok 13976 ms
[13:27:13] t/019_replslot_limit.pl .............. ok 10976 ms
[13:27:24] t/020_archive_status.pl .............. ok 6190 ms
[13:27:30] t/021_row_visibility.pl .............. ok 3227 ms
[13:27:33] t/022_crash_temp_files.pl ............ ok 2296 ms
[13:27:36] t/023_pitr_prepared_xact.pl .......... ok 3601 ms
[13:27:39] t/024_archive_recovery.pl ............ ok 3937 ms
[13:27:43] t/025_stuck_on_old_timeline.pl ....... ok 4348 ms
[13:27:47] t/026_standby_logical_decoding.pl .... ok 117730 ms <<<

Is it possible to improve this?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-08-26 11:42:08 Re: list of acknowledgments for PG14
Previous Message Amit Kapila 2021-08-26 11:12:56 Re: row filtering for logical replication