Postgres: Starting a subscription from "now" checkpoint

[mathantunes]

In the Subscription section of the docs, I found the following:

Subscriptions can subscribe from any position of a stream, but normally you'd subscribe from the beginning of the stream, which allows you to process all the historical events. For integration purposes, however, you would usually subscribe from now, as emitting historical events to other systems might produce undesired side effects.

I have a scenario where a new subscription is needed for integration purposes so I'd like to create a new subscription that starts from "now".

builder.Services.AddSubscription<PostgresAllStreamSubscription, PostgresAllStreamSubscriptionOptions>("integration-sub", b =>
{
    b
       .AddEventHandler<IntegrationHandler>()
       .UseCheckpointStore<PostgresCheckpointStore>();
});

Is there a way I can configure the checkpoint to start at the latest message rather than starting at NULL?
I can see a "manual" way where I create the subscription with a no-op handler and let it catch up to the latest checkpoint and then deploy a new version with the integration implementation but would be great if there was a native way of achieving this.

How should I set this up for new subscriptions? (Happy to update the docs with an example later 🙂 ).

I have also seen the AddGateway approach but internally it is also handled as a subscription from what I understood.

Thanks 🙏

[alexeyzimarev]

Hm, somehow it got missed. The start position is taken from the checkpoint store and if it doesn't exist, it will start from the beginning. There's no impediment to start from the end, but it's not implemented. Mind opening an issue?

[mathantunes]

#456