Hi Craig,
So, is it safe to drop those list from this query output?
select riname from pg_replication_identifier where riname not in
(select external_id from pg_replication_identifier_progress);
I cannot read pg_get_replication_identifier_progress function, is it likely
c function?
On Fri,
On 15 September 2017 at 11:46, milist ujang wrote:
> Hi Craig,
>
> Thanks again for pointing to inactive replication slot.
> After inactive replication slot been dropped, the relfrozenxid now moving.
>
> I wonder if replication identifier will have some issue if left
>
Hi Craig,
Thanks again for pointing to inactive replication slot.
After inactive replication slot been dropped, the relfrozenxid now moving.
I wonder if replication identifier will have some issue if left
un-chained? since at other side there are inactive replication identifier.
On Fri, Sep
On 14 September 2017 at 13:35, milist ujang wrote:
> HI list,
>
> I have a database with bdr environment which keep alerting these messages
> in log file:
>
> HINT: Close open transactions soon to avoid wraparound problems.
> WARNING: oldest xmin is far in the past
>
HI list,
I have a database with bdr environment which keep alerting these messages
in log file:
HINT: Close open transactions soon to avoid wraparound problems.
WARNING: oldest xmin is far in the past
Querying pg_stat_activity where state='active';
datname | template1
query