Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread Euler Taveira
On Mon, Oct 6, 2025, at 5:00 PM, Masahiko Sawada wrote: > I agree with your analysis. It seems there is no convenient way to > move RelationSyncCache inside PGOutputData. So let's proceed with the > proposed approach. > +1. Shouldn't we add a comment mentioning that it is a possibility? > I've do

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread vignesh C
On Fri, 26 Sept 2025 at 05:29, Masahiko Sawada wrote: > > On Thu, Jul 3, 2025 at 7:55 AM vignesh C wrote: > > > > On Wed, 2 Jul 2025 at 13:21, Zhijie Hou (Fujitsu) > > wrote: > > > > > > On Wed, Jul 2, 2025 at 2:42 PM vignesh C wrote: > > > > > > > > > > > Hi, > > > > > > > > I encountered an in

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread Euler Taveira
On Thu, Oct 9, 2025, at 10:40 AM, vignesh C wrote: > On Thu, 9 Oct 2025 at 00:16, Masahiko Sawada wrote: >> >> One thing we might want to consider is for v14 and v13. They don't >> have this bug since the entry_ctx was introduced in v15, but it's >> still true for them that RelationSyncCache is no

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread vignesh C
On Tue, 7 Oct 2025 at 23:40, Masahiko Sawada wrote: > > On Mon, Oct 6, 2025 at 6:55 PM Euler Taveira wrote: > > > > On Mon, Oct 6, 2025, at 5:00 PM, Masahiko Sawada wrote: > > > I agree with your analysis. It seems there is no convenient way to > > > move RelationSyncCache inside PGOutputData. So

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread Masahiko Sawada
On Mon, Oct 6, 2025 at 6:55 PM Euler Taveira wrote: > > On Mon, Oct 6, 2025, at 5:00 PM, Masahiko Sawada wrote: > > I agree with your analysis. It seems there is no convenient way to > > move RelationSyncCache inside PGOutputData. So let's proceed with the > > proposed approach. > > > > +1. Should

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread Masahiko Sawada
On Wed, Oct 8, 2025 at 11:39 AM vignesh C wrote: > > On Tue, 7 Oct 2025 at 23:40, Masahiko Sawada wrote: > > > > On Mon, Oct 6, 2025 at 6:55 PM Euler Taveira wrote: > > > > > > On Mon, Oct 6, 2025, at 5:00 PM, Masahiko Sawada wrote: > > > > I agree with your analysis. It seems there is no conven

Re: Invalid pointer access in logical decoding after error

2025-10-18 Thread Masahiko Sawada
On Thu, Oct 9, 2025 at 8:23 AM Euler Taveira wrote: > > On Thu, Oct 9, 2025, at 10:40 AM, vignesh C wrote: > > On Thu, 9 Oct 2025 at 00:16, Masahiko Sawada wrote: > >> > >> One thing we might want to consider is for v14 and v13. They don't > >> have this bug since the entry_ctx was introduced in

Re: Invalid pointer access in logical decoding after error

2025-10-17 Thread Masahiko Sawada
On Thu, Oct 9, 2025 at 10:07 AM Masahiko Sawada wrote: > > On Thu, Oct 9, 2025 at 8:23 AM Euler Taveira wrote: > > > > On Thu, Oct 9, 2025, at 10:40 AM, vignesh C wrote: > > > On Thu, 9 Oct 2025 at 00:16, Masahiko Sawada > > > wrote: > > >> > > >> One thing we might want to consider is for v14

Re: Invalid pointer access in logical decoding after error

2025-10-17 Thread vignesh C
On Thu, 9 Oct 2025 at 00:16, Masahiko Sawada wrote: > > On Wed, Oct 8, 2025 at 11:39 AM vignesh C wrote: > > > > On Tue, 7 Oct 2025 at 23:40, Masahiko Sawada wrote: > > > > > > On Mon, Oct 6, 2025 at 6:55 PM Euler Taveira wrote: > > > > > > > > On Mon, Oct 6, 2025, at 5:00 PM, Masahiko Sawada w

Re: Invalid pointer access in logical decoding after error

2025-10-12 Thread vignesh C
On Thu, 9 Oct 2025 at 23:33, Masahiko Sawada wrote: > > On Thu, Oct 9, 2025 at 10:07 AM Masahiko Sawada wrote: > > > > On Thu, Oct 9, 2025 at 8:23 AM Euler Taveira wrote: > > > > > > On Thu, Oct 9, 2025, at 10:40 AM, vignesh C wrote: > > > > On Thu, 9 Oct 2025 at 00:16, Masahiko Sawada > > > >

Re: Invalid pointer access in logical decoding after error

2025-10-06 Thread Masahiko Sawada
On Mon, Sep 29, 2025 at 1:52 AM vignesh C wrote: > > On Fri, 26 Sept 2025 at 05:29, Masahiko Sawada wrote: > > > > On Thu, Jul 3, 2025 at 7:55 AM vignesh C wrote: > > > > > > On Wed, 2 Jul 2025 at 13:21, Zhijie Hou (Fujitsu) > > > wrote: > > > > > > > > On Wed, Jul 2, 2025 at 2:42 PM vignesh C

Re: Invalid pointer access in logical decoding after error

2025-09-25 Thread Masahiko Sawada
On Thu, Jul 3, 2025 at 7:55 AM vignesh C wrote: > > On Wed, 2 Jul 2025 at 13:21, Zhijie Hou (Fujitsu) > wrote: > > > > On Wed, Jul 2, 2025 at 2:42 PM vignesh C wrote: > > > > > > > > Hi, > > > > > > I encountered an invalid pointer access issue. Below are the steps to > > > reproduce the issue: >

Re: Invalid pointer access in logical decoding after error

2025-07-03 Thread vignesh C
On Wed, 2 Jul 2025 at 13:21, Zhijie Hou (Fujitsu) wrote: > > On Wed, Jul 2, 2025 at 2:42 PM vignesh C wrote: > > > > > Hi, > > > > I encountered an invalid pointer access issue. Below are the steps to > > reproduce the issue: > ... > > The error occurs because entry->columns is allocated in the en

RE: Invalid pointer access in logical decoding after error

2025-07-02 Thread Zhijie Hou (Fujitsu)
On Wed, Jul 2, 2025 at 2:42 PM vignesh C wrote: > > Hi, > > I encountered an invalid pointer access issue. Below are the steps to > reproduce the issue: ... > The error occurs because entry->columns is allocated in the entry > private context (entry->entry_cxt) by pub_collist_to_bitmapset(). T

Invalid pointer access in logical decoding after error

2025-07-01 Thread vignesh C
Hi, I encountered an invalid pointer access issue. Below are the steps to reproduce the issue: -- Create table CREATE TABLE t1(c1 int, c2 int); -- Create publications with each publication selecting a different column CREATE PUBLICATION pub1 for TABLE t1(c1); CREATE PUBLICATION pub2 for TABLE t1