Re: pgarchives: issue (?) when responding to a message on another list

From: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
To: pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: pgarchives: issue (?) when responding to a message on another list
Date: 2023-10-31 18:23:03
Message-ID: 13f1b001-bd4e-4808-8e1a-07fe7861559f@cmatte.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Ping on this as I'd like to know if I should deploy as-is. Is this expected behaviour that responses on list B to a message originally on list A get archived on both lists?

On 19/10/2023 19:36, Célestin Matte wrote:
> I've fixed the issue with primary keys listed in another thread [1] and now encounter a strange behaviour when testing: responding to a message on a different list than the original recipient list saves this message in both lists' archives (it is saved in the database once, but appears on both lists). I'm now wondering if this is expected behaviour or a problem in my fix or install.
> Given that messages belong to threads (and not lists), which can belong to several lists, I guess this is the intended behaviour.
>
> This use case happens for instance when a user responds to a message posted in an *-announce list to a more general list. In such case, it is inappropriate to archive the message in the more restricted *-announce list.
> I've looked for an example in postgresql archives to see if this happens in the deployment for postgresql but haven't managed to find one as it's pretty rare.
>
> [1]: https://www.postgresql.org/message-id/CABUevExzjRo-=9Hg4CDdnGHuQB1L6uAwekni0mz-1CECaMcGZA@mail.gmail.com

--
Célestin Matte

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Magnus Hagander 2023-11-01 15:29:11 Re: pgarchives: issue (?) when responding to a message on another list
Previous Message Joe Conway 2023-10-31 16:04:37 Re: Wiki editor request