Thanks for letting us know, will be happy to see it appear.
Regards,
Koen De Groote
On Thu, Nov 21, 2024 at 11:15 PM Bruce Momjian wrote:
> On Thu, Oct 31, 2024 at 06:52:34PM -0400, Bruce Momjian wrote:
> > On Fri, Nov 1, 2024 at 09:07:38AM +1100, Peter Smith wrote:
> > > O
And my thanks to everyone who took part.
Regards,
Koen De Groote
On Thu, Oct 31, 2024 at 4:16 PM Bruce Momjian wrote:
> On Fri, Oct 25, 2024 at 11:48:16PM +0200, Koen De Groote wrote:
> > Number 2 would be perfect, I think. It leaves no doubt at all.
>
> I went with even more
Number 2 would be perfect, I think. It leaves no doubt at all.
Regards,
Koen De Groote
On Fri, Oct 25, 2024 at 9:32 AM Laurenz Albe
wrote:
> On Fri, 2024-10-25 at 17:22 +1100, Peter Smith wrote:
> > It seems to me the same clarification could be achieved just by adding
> > 1 wo
most people aren't going to take time for.
At least, that's how I see the situation. It may be presumptive of me.
I realize this has taken a bit of time already, and for my part, I would
like the more explicit statement, as shown by Laurenz, but I'm not going to
keep going on about
e typically starts, a snapshot is
> taken of the table's data on the publisher database and copied to the
> subscriber
Does not clarify that.
It's the reason I created this mail: I would like it stated explicitly that
the database process takes care of this for us.
Regards,
Koen
n the publisher are sent"
to
"publisher database. Once complete, any changes on the publisher since the
initial copy are sent"
Hope that's ok.
Thanks for looking into this.
Regards,
Koen De Groote
On Thu, Oct 17, 2024 at 3:20 AM Bruce Momjian wrote:
> On Sat, May 18
Yes, this change is clear to me that the "columns added" applies to the
table on the publisher.
Regards,
Koen De Groote
On Tue, Jun 4, 2024 at 7:57 AM Amit Kapila wrote:
> On Fri, May 31, 2024 at 10:54 PM Peter Smith
> wrote:
> >
> > On Wed, May 29, 2024
