Re: [PATCH] pgarchives: Bugfix: missing ids in pglister_sync

From: Célestin Matte <celestin(dot)matte(at)cmatte(dot)me>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-www(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] pgarchives: Bugfix: missing ids in pglister_sync
Date: 2023-02-21 17:33:05
Message-ID: 8a510361-1d62-5a1e-399d-40bed1bb37de@cmatte.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Hello,

This patch was never merge into master, the issue still exists. I think it's been forgotten.
Can it be merged now?

On 30/01/2022 13:32, Magnus Hagander wrote:
> On Fri, Jan 28, 2022 at 6:52 PM Célestin Matte <celestin(dot)matte(at)cmatte(dot)me> wrote:
>>
>> groupid and listid are not explicitly set in pglister_sync's queries, which
>> causes the script to fail as these fields are NOT NULL and postgresql default
>> configuration does not auto-fill id fields.
>>
>> This patch sets them explicitly by reusing the ones obtained from pglister.
>
> These fields are supposed to be serial fields, not pure integers, I
> think. This feels like some very old legacy that hasn't been properly
> fixed.
>
> I think the attached patch is more correct (I've backpatched it into
> the 0001 migration because making it a separate migration makes it
> somewhat destructive -- it's easier to just change it manually on
> existing installs if you have one)
>

--
Célestin Matte

In response to

Browse pgsql-www by date

  From Date Subject
Next Message Peter Geoghegan 2023-02-21 18:56:39 Re: Doc images are broken
Previous Message Célestin Matte 2023-02-21 16:49:05 Re: [PATCHES] pgarchives: merge schema.sql into Django's model