Hi Team,
One of the queries, which retrieves a single record from a table with 16
hash partitions, is taking more than 10 seconds to execute. In contrast,
when we run the same query manually, it completes within milliseconds. This
issue is causing exhaustion of the application pools. Do we have an
an option available to handle this
scenario? *
Regards,
Ram.
On Wed, 25 Sept 2024 at 20:12, Greg Sabino Mullane
wrote:
> On Sat, Sep 21, 2024 at 3:08 PM Ramakrishna m wrote:
>
>> I would greatly appreciate any suggestions you may have to help avoid
>> logical replication delay
isher and subscriber has to do.
>
> Hope this helps.
>
>
>
> On Sat, Sep 21, 2024 at 3:08 PM Ramakrishna m wrote:
>
>> Hi Team,
>>
>> We have configured bidirectional replication (but traffic can only flow
>> in one direction) between two data centers (dist
Hi Team,
We have configured bidirectional replication (but traffic can only flow in
one direction) between two data centers (distance: 1000 km, maximum Network
latency: 100 ms) with an application TPS (transactions per second) of 700
at maximum.
We are fine with handling up to 500 TPS without obs
Hi Team,
adding one more point here,
5. Pg_stat_replication_slot total_txn count reduces when lag occurs .Does
decoding stop in case of logical replication delay?
On Tue, 23 Apr 2024 at 22:55, Ramakrishna m wrote:
> Hi Team,
>
> I am facing replication lag in postgres16 at times
Hi Team,
I am facing replication lag in postgres16 at times,not able to find the
reason.
Please find the configuration:
1) Two replication slots for two servers (1 is the same data center,
another remote)
2) weekly once/twice facing lag(around 2GB for 1k TPS environment) in the
remote replicati
