On Sat, Jul 26, 2025 at 3:13 PM Igor Korot wrote:
>
> I didn't find the sorting for the field.
>
> Can you help?
The pg_index_column_has_property() can provide this information. E.g.,
select pg_index_column_has_property('my_index'::regclass, 2, 'desc');
On Fri, Jul 25, 2025 at 7:13 PM Greg Sabino Mullane wrote:
>
> On Fri, Jul 25, 2025 at 9:57 AM Jon Zeppieri wrote:
>>
>> Thanks for the response, Nick. I'm curious why the situation you describe
>> wouldn't also lead to the write_lag and flush_lag also being
On Wed, Jul 23, 2025 at 4:27 PM Nick Cleaton wrote:
>
> On Fri, 18 Jul 2025 at 21:29, Jon Zeppieri wrote:
> >
> > I just had a situation where physical replication fell far behind
> > (hours). The write and flush lag times were 0, but replay_lag was
> > high. The re
Hi,
I just had a situation where physical replication fell far behind
(hours). The write and flush lag times were 0, but replay_lag was
high. The replica has hot_standby_feedback on, and both
max_standby_streaming_delay and max_standby_archive_delay are set to
30s.
What could cause a situation li
