Only one consumer is receiving existing messages when they're created after the messages have been sent

[alandecastros]

Describe the bug
I've made the following test
In this publisher application I'm using the following configuration:

builder.Host.UseWolverine(x =>
{
    x.UsePostgresqlPersistenceAndTransport(
        "connectionString...",
        schema: "wolverine",
        transportSchema: "wolverine"
    );

    x.PublishMessage<MyRequest>().ToPostgresqlQueue("my-request");
});

And published some messages before starting any consumer.

for (var i = 0; i < 100; i++)
{
    await bus.SendAsync(new MyRequest("test"));
}

Then I started sequentially two consumer apps with the following configuration:

builder.Host.UseWolverine(x =>
{
    x.UsePostgresqlPersistenceAndTransport(
        "User ID=postgres;Password=postgres;Host=localhost;Port=5432;Database=acoesdb;Pooling=true",
        schema: "wolverine",
        transportSchema: "wolverine"
    );

    x.ListenToPostgresqlQueue("my-request").MaximumParallelMessages(1);
});

Only the first consumer gets the messages.

Am I missing a configuration? It's a bug or that's the way it's suppose to work?

[jeremydmiller]

@alandecastros Hey man, please use Discord for questions in the future rather than GitHub issues. The postgresql queue is competing consumers all the way. If you want to do a fan out, you'll need to use something different, or a queue per listener