Mmm..
At Tue, 29 Oct 2019 13:57:19 +0900 (JST), Kyotaro Horiguchi
wrote in
> So, somehow we need to complete the KnownAssignedTransactionIds even
> if there's any subxid-overflown transactions. As mentioned upthread,
> I think we have at least the following choices.
>
> - Send back the complet
At Thu, 24 Oct 2019 17:37:52 +0800 (CST), Thunder wrote in
> Thanks for replay.I feel confused about snapshot.
>
> At 2019-10-23 11:51:19, "Kyotaro Horiguchi" wrote:
> >Hello.
> >
> >At Tue, 22 Oct 2019 20:42:21 +0800 (CST), Thunder wrote
> >in
> >> Update the patch.
> >>
> >> 1. The STAN
Hi
In our usage scenario the standby node could be OOM killed and we have to
create new standby node.
If master node has uncommitted long transaction and new standby node can not
provide service.
So for us this is a critical issue.
I do hope any suggestion to this issue.
And can any one help to
Thanks for replay.I feel confused about snapshot.
At 2019-10-23 11:51:19, "Kyotaro Horiguchi" wrote:
>Hello.
>
>At Tue, 22 Oct 2019 20:42:21 +0800 (CST), Thunder wrote in
>> Update the patch.
>>
>> 1. The STANDBY_SNAPSHOT_PENDING state is set when we replay the first
>> XLOG_RUNNING_XACTS an
At Wed, 23 Oct 2019 12:51:19 +0900 (JST), Kyotaro Horiguchi
wrote in
> Hello.
>
> At Tue, 22 Oct 2019 20:42:21 +0800 (CST), Thunder wrote
> in
> > Update the patch.
> >
> > 1. The STANDBY_SNAPSHOT_PENDING state is set when we replay the first
> > XLOG_RUNNING_XACTS and the sub transaction
Hello.
At Tue, 22 Oct 2019 20:42:21 +0800 (CST), Thunder wrote in
> Update the patch.
>
> 1. The STANDBY_SNAPSHOT_PENDING state is set when we replay the first
> XLOG_RUNNING_XACTS and the sub transaction ids are overflow.
> 2. When we log XLOG_RUNNING_XACTS in master node, can we assume that
Update the patch.
1. The STANDBY_SNAPSHOT_PENDING state is set when we replay the first
XLOG_RUNNING_XACTS and the sub transaction ids are overflow.
2. When we log XLOG_RUNNING_XACTS in master node, can we assume that all xact
IDS < oldestRunningXid are considered finished?
3. If we can assume t
On Mon, Oct 21, 2019 at 4:13 AM Thunder wrote:
> Can we fix this issue like the following patch?
>
> $git diff src/backend/access/transam/xlog.c
> diff --git a/src/backend/access/transam/xlog.c
> b/src/backend/access/transam/xlog.c
> index 49ae97d4459..0fbdf6fd64a 100644
> --- a/src/backend/acces
Can we fix this issue like the following patch?
$git diff src/backend/access/transam/xlog.c
diff --git a/src/backend/access/transam/xlog.c
b/src/backend/access/transam/xlog.c
index 49ae97d4459..0fbdf6fd64a 100644
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@
Hi hackers,
I found this issue when restart standby node and then try to connect it.
It return "psql: FATAL: the database system is starting up".
The steps to reproduce this issue.
1. Create a session to run uncommit_trans.sql
2. Create the other session to do checkpoint
3. Restart standby no
10 matches
Mail list logo