On Sat, Sep 27, 2025 at 9:24 PM Dilip Kumar wrote:
>
> On Sat, Sep 27, 2025 at 8:53 PM Amit Kapila wrote:
> >
> > I am not able to understand what exact problem you are seeing here. I
> > was thinking that during the CREATE SUBSCRIPTION command, a new table
> > with user provided name will be cre
On Sat, Sep 27, 2025 at 8:53 PM Amit Kapila wrote:
>
> I am not able to understand what exact problem you are seeing here. I
> was thinking that during the CREATE SUBSCRIPTION command, a new table
> with user provided name will be created similar to how we create a
> slot. The difference would be
On Fri, Sep 26, 2025 at 4:42 PM Dilip Kumar wrote:
>
> On Thu, Sep 25, 2025 at 4:19 PM Dilip Kumar wrote:
> >
> > On Thu, Sep 25, 2025 at 11:53 AM Dilip Kumar wrote:
> > >
> > > > [1]
> > > > /*
> > > > * For logical decode we need combo CIDs to properly decode the
> > > > * catalog
> > > > */
>
On Thu, Sep 25, 2025 at 4:19 PM Dilip Kumar wrote:
>
> On Thu, Sep 25, 2025 at 11:53 AM Dilip Kumar wrote:
> >
> > > [1]
> > > /*
> > > * For logical decode we need combo CIDs to properly decode the
> > > * catalog
> > > */
> > > if (RelationIsAccessibleInLogicalDecoding(relation))
> > > log_heap
On Thu, Sep 25, 2025 at 11:53 AM Dilip Kumar wrote:
>
> > [1]
> > /*
> > * For logical decode we need combo CIDs to properly decode the
> > * catalog
> > */
> > if (RelationIsAccessibleInLogicalDecoding(relation))
> > log_heap_new_cid(relation, &tp);
> >
>
> Meanwhile I am also exploring the optio
On Thu, Sep 25, 2025 at 11:09 AM Dilip Kumar wrote:
>
> On Sat, Sep 20, 2025 at 5:29 PM Amit Kapila wrote:
> >
> > On Thu, Sep 18, 2025 at 11:46 PM Masahiko Sawada
> > wrote:
> > >
> > > On Thu, Sep 18, 2025 at 1:33 AM Amit Kapila
> > > wrote:
> > > >
> > > > If we compare conflict_history_ta
On Tue, Sep 23, 2025 at 11:29 PM Masahiko Sawada wrote:
>
> On Sat, Sep 20, 2025 at 4:59 AM Amit Kapila wrote:
> >
> > On Thu, Sep 18, 2025 at 11:46 PM Masahiko Sawada
> > wrote:
> > >
> > > On Thu, Sep 18, 2025 at 1:33 AM Amit Kapila
> > > wrote:
> > > >
> > > > If we compare conflict_histor
On Thu, Sep 11, 2025 at 8:43 AM Amit Kapila wrote:
>
> On Thu, Sep 11, 2025 at 12:53 AM Bharath Rupireddy
> wrote:
> >
> > On Tue, Aug 5, 2025 at 5:24 AM Dilip Kumar wrote:
> > >
> > > Currently we log conflicts to the server's log file and updates, this
> > > approach has limitations, 1) Diffic
On Thu, Sep 18, 2025 at 11:46 PM Masahiko Sawada wrote:
>
> On Thu, Sep 18, 2025 at 1:33 AM Amit Kapila wrote:
> >
> > If we compare conflict_history_table with the slot that gets created
> > with subscription, one can say the same thing about slots. Users can
> > drop the slots and whole replica
On Wed, Sep 10, 2025 at 4:32 PM Alastair Turner wrote:
>
>> Here we will have to create a built-in type of type table which is I
>> think typcategory => 'C' and if we create this type it should be
>> supplied with the "typrelid" that means there should be a backing
>> catalog table. At least thats
On Sun, Sep 14, 2025 at 12:23 PM Dilip Kumar wrote:
>
> On Sat, Sep 13, 2025 at 6:16 AM Bharath Rupireddy
> wrote:
>
> Thanks for the feedback Bharath
>
> > On Fri, Sep 12, 2025 at 3:13 AM Dilip Kumar wrote:
> > >
> > > I was looking into another thread where we provide an error table for
> > >
On Thu, Sep 18, 2025 at 1:33 AM Amit Kapila wrote:
>
> On Sun, Sep 14, 2025 at 12:23 PM Dilip Kumar wrote:
> >
> > On Sat, Sep 13, 2025 at 6:16 AM Bharath Rupireddy
> > wrote:
> >
> > Thanks for the feedback Bharath
> >
> > > On Fri, Sep 12, 2025 at 3:13 AM Dilip Kumar wrote:
> > > >
> > > > I
On Thu, Sep 18, 2025 at 2:03 PM Amit Kapila wrote:
>
> On Sun, Sep 14, 2025 at 12:23 PM Dilip Kumar wrote:
> >
> > On Sat, Sep 13, 2025 at 6:16 AM Bharath Rupireddy
> > wrote:
> >
> > Thanks for the feedback Bharath
> >
> > > On Fri, Sep 12, 2025 at 3:13 AM Dilip Kumar wrote:
> > > >
> > > > I
On Sat, Sep 13, 2025 at 6:16 AM Bharath Rupireddy
wrote:
Thanks for the feedback Bharath
> On Fri, Sep 12, 2025 at 3:13 AM Dilip Kumar wrote:
> >
> > I was looking into another thread where we provide an error table for
> > COPY [1], it requires the user to pre-create the error table. And
> > i
Hi,
On Fri, Sep 12, 2025 at 3:13 AM Dilip Kumar wrote:
>
> I was looking into another thread where we provide an error table for
> COPY [1], it requires the user to pre-create the error table. And
> inside the COPY command we will validate the table, validation in that
> context is a one-time pro
Hi,
On Wed, Sep 10, 2025 at 8:13 PM Amit Kapila wrote:
>
> > How about streaming the conflicts in fixed format to a separate log
> > file other than regular postgres server log file?
>
> I would prefer this info to be stored in tables as it would be easy to
> query them. If we use separate LOGs t
On Mon, Sep 8, 2025 at 12:01 PM Dilip Kumar wrote:
>
> On Sun, Sep 7, 2025 at 1:42 PM Alastair Turner wrote:
> >
> > Hi Dilip
> >
> > Thanks for working on this, I think it will make conflict detection a lot
> > more useful.
>
> Thanks for the suggestions, please find my reply inline.
>
> > On S
On Thu, Sep 11, 2025 at 12:53 AM Bharath Rupireddy
wrote:
>
> On Tue, Aug 5, 2025 at 5:24 AM Dilip Kumar wrote:
> >
> > Currently we log conflicts to the server's log file and updates, this
> > approach has limitations, 1) Difficult to query and analyze, parsing
> > plain text log files for confl
Hi,
On Tue, Aug 5, 2025 at 5:24 AM Dilip Kumar wrote:
>
> Currently we log conflicts to the server's log file and updates, this
> approach has limitations, 1) Difficult to query and analyze, parsing
> plain text log files for conflict details is inefficient. 2) Lack of
> structured data, key conf
On Wed, 10 Sept 2025 at 11:15, Dilip Kumar wrote:
> On Wed, Sep 10, 2025 at 3:25 PM Amit Kapila
> wrote:
> >
>
...
> >
> > How about having this as a built-in type?
>
> Here we will have to create a built-in type of type table which is I
> think typcategory => 'C' and if we create this type it
On Wed, Sep 10, 2025 at 3:25 PM Amit Kapila wrote:
>
> On Mon, Sep 8, 2025 at 12:01 PM Dilip Kumar wrote:
> >
> > On Sun, Sep 7, 2025 at 1:42 PM Alastair Turner wrote:
> > >
> > > Hi Dilip
> > >
> > > Thanks for working on this, I think it will make conflict detection a lot
> > > more useful.
>
On Sun, Sep 7, 2025 at 1:42 PM Alastair Turner wrote:
>
> Hi Dilip
>
> Thanks for working on this, I think it will make conflict detection a lot
> more useful.
Thanks for the suggestions, please find my reply inline.
> On Sat, 6 Sept 2025, 10:38 Dilip Kumar, wrote:
>>
>> While working on the p
Hi Dilip
Thanks for working on this, I think it will make conflict detection a lot
more useful.
On Sat, 6 Sept 2025, 10:38 Dilip Kumar, wrote:
> While working on the patch, I see there are some open questions
>
> 1. We decided to pass the conflict history table name during
> subscription creati
On Thu, Aug 21, 2025 at 9:17 AM Dilip Kumar wrote:
>
> On Wed, Aug 20, 2025 at 5:46 PM Amit Kapila wrote:
> >
> > On Wed, Aug 20, 2025 at 11:47 AM Dilip Kumar wrote:
> > >
> > > On Mon, Aug 18, 2025 at 12:25 PM Amit Kapila
> > > wrote:
> > > >
> > >
> > > > One idea to keep things simple for t
On Wed, Aug 20, 2025 at 5:46 PM Amit Kapila wrote:
>
> On Wed, Aug 20, 2025 at 11:47 AM Dilip Kumar wrote:
> >
> > On Mon, Aug 18, 2025 at 12:25 PM Amit Kapila
> > wrote:
> > >
> >
> > > One idea to keep things simple for the first version is that we allow
> > > users to specify the table_name
On Wed, Aug 20, 2025 at 11:47 AM Dilip Kumar wrote:
>
> On Mon, Aug 18, 2025 at 12:25 PM Amit Kapila wrote:
> >
>
> > One idea to keep things simple for the first version is that we allow
> > users to specify the table_name for storing conflicts but the table
> > should be created internally and
On Mon, Aug 18, 2025 at 12:25 PM Amit Kapila wrote:
>
> On Fri, Aug 15, 2025 at 2:31 PM Dilip Kumar wrote:
> >
> > Yet another question is about table names, whether we keep some
> > standard name like conflict_log_history_$subid or let users pass the
> > name.
> >
>
> It would be good if we can
On Fri, Aug 15, 2025 at 2:31 PM Dilip Kumar wrote:
>
> Yet another question is about table names, whether we keep some
> standard name like conflict_log_history_$subid or let users pass the
> name.
>
It would be good if we can let the user specify the table_name and if
she didn't specify then use
On Wed, Aug 13, 2025 at 3:39 PM Amit Kapila wrote:
>
> On Fri, Aug 8, 2025 at 10:01 AM Dilip Kumar wrote:
> >
> > On Fri, Aug 8, 2025 at 8:58 AM shveta malik wrote:
> > >
> > > On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
> > > >
> > > > So logically for PostgreSQL its an
> > > > user tabl
On Thu, Aug 14, 2025 at 4:26 PM Alastair Turner wrote:
>
> On Wed, 13 Aug 2025 at 11:09, Amit Kapila wrote:
>>
>> On Fri, Aug 8, 2025 at 10:01 AM Dilip Kumar wrote:
>> >
>> > On Fri, Aug 8, 2025 at 8:58 AM shveta malik wrote:
>> > >
>> > > On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
>> >
On Wed, 13 Aug 2025 at 11:09, Amit Kapila wrote:
> On Fri, Aug 8, 2025 at 10:01 AM Dilip Kumar wrote:
> >
> > On Fri, Aug 8, 2025 at 8:58 AM shveta malik
> wrote:
> > >
> > > On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar
> wrote:
> > > >
> > > > So logically for PostgreSQL its an
> > > > user tab
On Fri, Aug 8, 2025 at 10:01 AM Dilip Kumar wrote:
>
> On Fri, Aug 8, 2025 at 8:58 AM shveta malik wrote:
> >
> > On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
> > >
> > > So logically for PostgreSQL its an
> > > user table but yeah this is created and managed by the extension.
> > >
> >
> >
On Fri, Aug 8, 2025 at 10:01 AM Dilip Kumar wrote:
>
> On Fri, Aug 8, 2025 at 8:58 AM shveta malik wrote:
> >
> > On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
> > >
> > > So logically for PostgreSQL its an
> > > user table but yeah this is created and managed by the extension.
> > >
> >
> >
On Fri, Aug 8, 2025 at 8:58 AM shveta malik wrote:
>
> On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
> >
> > So logically for PostgreSQL its an
> > user table but yeah this is created and managed by the extension.
> >
>
> Any idea if the user can alter/drop or perform any DML on it? I could
>
On Thu, Aug 7, 2025 at 3:08 PM Dilip Kumar wrote:
>
> On Thu, Aug 7, 2025 at 1:43 PM shveta malik wrote:
> >
> > On Thu, Aug 7, 2025 at 12:25 PM shveta malik wrote:
>
> Thanks Shveta for your opinion on the design.
>
> > > On Tue, Aug 5, 2025 at 5:54 PM Dilip Kumar wrote:
> > > >
>
> > > > This
On Thu, Aug 7, 2025 at 1:43 PM shveta malik wrote:
>
> On Thu, Aug 7, 2025 at 12:25 PM shveta malik wrote:
Thanks Shveta for your opinion on the design.
> > On Tue, Aug 5, 2025 at 5:54 PM Dilip Kumar wrote:
> > >
> > > This proposal aims to address these limitations by introducing a
> > > con
On Thu, Aug 7, 2025 at 12:25 PM shveta malik wrote:
>
> On Tue, Aug 5, 2025 at 5:54 PM Dilip Kumar wrote:
> >
> > Currently we log conflicts to the server's log file and updates, this
> > approach has limitations, 1) Difficult to query and analyze, parsing
> > plain text log files for conflict de
On Tue, Aug 5, 2025 at 5:54 PM Dilip Kumar wrote:
>
> Currently we log conflicts to the server's log file and updates, this
> approach has limitations, 1) Difficult to query and analyze, parsing
> plain text log files for conflict details is inefficient. 2) Lack of
> structured data, key conflict
38 matches
Mail list logo
