MIME-Version: 1.0
References: <d38cae77-b5fc-4dc2-9ff3-4f51665f8364@cmatte.me>
 <13f1b001-bd4e-4808-8e1a-07fe7861559f@cmatte.me>
In-Reply-To: <13f1b001-bd4e-4808-8e1a-07fe7861559f@cmatte.me>
From: Magnus Hagander <magnus@hagander.net>
Date: Wed, 1 Nov 2023 16:29:11 +0100
Message-ID: 
 <CABUevEwpzAAS63c8BUcXV86XoiipGoe_uk6EL7Pz0QjQqhxVqQ@mail.gmail.com>
Subject: Re: pgarchives: issue (?) when responding to a message on another
 list
To: =?UTF-8?Q?C=C3=A9lestin_Matte?= <celestin.matte@cmatte.me>
Cc: pgsql-www@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CABUevEwpzAAS63c8BUcXV86XoiipGoe_uk6EL7Pz0QjQqhxVqQ%40mail.gmail.com>
Precedence: bulk

Hi!

Apologies - I remember seeing the original one, and I thought I had
actually answered it.

Yes, this is entirely by design, so your analysis is correct.

//Magnus


On Tue, Oct 31, 2023 at 7:23=E2=80=AFPM C=C3=A9lestin Matte <celestin.matte=
@cmatte.me> wrote:
>
> Ping on this as I'd like to know if I should deploy as-is. Is this expect=
ed 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=C3=A9lestin 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 bo=
th lists' archives (it is saved in the database once, but appears on both l=
ists). I'm now wondering if this is expected behaviour or a problem in my f=
ix 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 po=
sted in an *-announce list to a more general list. In such case, it is inap=
propriate to archive the message in the more restricted *-announce list.
> > I've looked for an example in postgresql archives to see if this happen=
s 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-=3D9Hg4CDdnGHuQ=
B1L6uAwekni0mz-1CECaMcGZA@mail.gmail.com
>
> --
> C=C3=A9lestin Matte
>
>