Hi
On Fri, Aug 2, 2024 at 1:28 PM KK CHN wrote:
> Thank you for shedding light on this.
>
> On Thu, Aug 1, 2024 at 4:04 PM Mateusz Henicz
> wrote:
>
>> When you are performing PITR you need to configure a timestamp before
>> your last committed transaction. In your case you provided timestamp a
Thank you for shedding light on this.
On Thu, Aug 1, 2024 at 4:04 PM Mateusz Henicz
wrote:
> When you are performing PITR you need to configure a timestamp before your
> last committed transaction. In your case you provided timestamp after your
> last commit.
>
>
I am trying to understand this
sorry ignore the previous paste , was in complete
Here the full one. https://pastecode.io/s/hya0fyvo
On Thu, Aug 1, 2024 at 4:02 PM KK CHN wrote:
> The logs are here.
>
> https://pastecode.io/s/s5dp8ur1
>
>
>
> On Thu, Aug 1, 2024 at 3:30 PM Kashif Zeeshan
> wrote:
>
>> Hi
>>
>> On Thu, Aug
When you are performing PITR you need to configure a timestamp before your
last committed transaction. In your case you provided timestamp after your
last commit.
When postgtes is restoring until a specified point, it restores a
transaction from WAL, and checking if next transaction is before or a
The logs are here.
https://pastecode.io/s/s5dp8ur1
On Thu, Aug 1, 2024 at 3:30 PM Kashif Zeeshan
wrote:
> Hi
>
> On Thu, Aug 1, 2024 at 2:54 PM KK CHN wrote:
>
>> List,
>>
>> *Not working (start EPAS server always fails):*
>>
>> 1. Testing PTR using PgBackRest(2.52.1) on RHEL9 EPAS-16, an
Hi
On Thu, Aug 1, 2024 at 2:54 PM KK CHN wrote:
> List,
>
> *Not working (start EPAS server always fails):*
>
> 1. Testing PTR using PgBackRest(2.52.1) on RHEL9 EPAS-16, and RHEL9 (
> Repo Server)
>
> When I do a PTR
>
> 1. After doing a table drop and then
> 2. Noting down the time
