Re: Accidental setting of XLogReaderState.private_data ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Accidental setting of XLogReaderState.private_data ?
Date
Msg-id 21321.1555340778@sss.pgh.pa.us
Whole thread Raw
In response to Accidental setting of XLogReaderState.private_data ?  (Antonin Houska <ah@cybertec.at>)
Responses Re: Accidental setting of XLogReaderState.private_data ?
List pgsql-hackers
Antonin Houska <ah@cybertec.at> writes:
> StartupDecodingContext() initializes ctx->reader->private_data with ctx, and
> it even does so twice. I couldn't find a place in the code where the
> (LogicalDecodingContext *) pointer is retrieved from the reader, and a simple
> test of logical replication works if the patch below is applied. Thus I assume
> that assignment is a thinko, isn't it?

Hmm.  The second, duplicate assignment is surely pointless, but I think
that setting the ctx as the private_data is a good idea.  It hardly seems
out of the question that it might be needed in future.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: partitioning performance tests after recent patches
Next
From: Tom Lane
Date:
Subject: Re: Zedstore - compressed in-core columnar storage