Re: pgsql: Respect permissions within logical replication.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Jeff Davis <jdavis(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Respect permissions within logical replication.
Date: 2022-01-09 18:02:56
Message-ID: d5bc9ade7b1e1d1a5af2501af34bee00c65ecb20.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, 2022-01-08 at 11:56 +0530, Amit Kapila wrote:
> One possible reason for this failure could be that the test doesn't
> wait for the initial sync to complete after CREATE SUBSCRIPTION which
> can allow more than expected operations to be replicated. Also, the
> reason it passes in other machines is that in those runs initial sync
> could get finished before we start to publish other operations.

You're right, even though the initial table is empty. I copied some
code from a different test to wait for the sync, and it appears to be
succeeding now.

Thanks,
Jeff Davis

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2022-01-09 18:08:04 Re: pgsql: Respect permissions within logical replication.
Previous Message Tom Lane 2022-01-09 17:43:16 pgsql: Make pg_get_expr() more bulletproof.