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
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 attributes (table, operation, old/new
data, LSN, etc.) are no
15 matches
Mail list logo
