Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1meI32-0004ve-IF for pgsql-www@arkaria.postgresql.org; Sat, 23 Oct 2021 14:31:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1meI30-0006we-7r for pgsql-www@arkaria.postgresql.org; Sat, 23 Oct 2021 14:30:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1meI30-0006va-1a for pgsql-www@lists.postgresql.org; Sat, 23 Oct 2021 14:30:58 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1meI2x-0004JQ-4P for pgsql-www@lists.postgresql.org; Sat, 23 Oct 2021 14:30:57 +0000 Received: by mail-lj1-x235.google.com with SMTP id d13so1390927ljg.0 for ; Sat, 23 Oct 2021 07:30:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kj2RtbAaFl9tH0NjoXn9wgbmuH9pcEKIKZ/r0LNskWg=; b=5uGJnuWgOsJkf28ljedrwcKAqj0DQbzIBxjy8BK2uJzyyGTJLl4paqtiWZvphmFF/2 dyCjV6NOqUUFmZX0e/Y+aIvAgSY8tfNgF360B3unF0wMDkUtM2yG8Kv/DKf1BG6jboJj 3qVjQY/VooTiFA/F2R8UlCHx3eaISsDCuHdggJK/qShfcezluhP/LtOgVtuBPfKFlLvR Ic+VMR2TVTwsTf2LYcaUwvkk1zBJHpIQyA3rtmGL/svqO77yEKVTofWWKVRhWGl90hrW H6EW/UVCN0Z36p5KyJer2qTVl5ODCGL7qxhYOq/tPezHuwWhbg0skxukb3O6kBj8iHjf agHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kj2RtbAaFl9tH0NjoXn9wgbmuH9pcEKIKZ/r0LNskWg=; b=78Quuiul2tUmUgdD1CJ0PsfzqEwAJAZ0RWAUBdGqM+sCn84x44/w/gTm000IjKzr47 0L1IX8XsO9Ccp3MMA52dvWcX8rT/df01o2jEeDKMBXcPyRyOEXND1yghB1Z6ScSdEMBb 3DhkmEV0m0qyaD+3C4AE2miCAO/At820yLOmo6VKJApCkGWMPy3FzpepA4/3DsBWuaAN R50If5uALh0hrPg+Z4TsCMJ0tjRyJagzD7G9nZwjtiIwhK/eu/XPP//UL66KBsS32MvB 8E6TC5g17M8iuVIgJaZtWlBs/l1uDosS78pt3XoXBrEY6kmcAKMG86cLJwZvFOyRAypy i8HA== X-Gm-Message-State: AOAM530QcQPie6mvWz5tOEinIYTKVXJz84h42TAKJxwcMpTx0m07/nAw f2ZHehRaC3RTV+h+Yas2OS1Za8LjiICfDmBBUbwE0g== X-Google-Smtp-Source: ABdhPJwp2m0GO9/+wGGxJUXZUwYAHtqV3gUromEBp3GmqthrqXgzdeSBYpqyfDTpJ2TgAIfe75CgyCMdzQKXtvOmI+8= X-Received: by 2002:a2e:a26c:: with SMTP id k12mr7034008ljm.23.1634999454318; Sat, 23 Oct 2021 07:30:54 -0700 (PDT) MIME-Version: 1.0 References: <71f7adb0-8588-a695-acad-f7034d3315d4@cmatte.me> In-Reply-To: <71f7adb0-8588-a695-acad-f7034d3315d4@cmatte.me> From: Magnus Hagander Date: Sat, 23 Oct 2021 16:30:43 +0200 Message-ID: Subject: Re: [PATCH] pgarchives: Fix database install procedure: remove redundant tables in schema.sql To: =?UTF-8?Q?C=C3=A9lestin_Matte?= , "Jonathan S. Katz" Cc: PostgreSQL WWW Content-Type: multipart/alternative; boundary="000000000000aed30b05cf05f947" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aed30b05cf05f947 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Oct 22, 2021 at 5:20 PM C=C3=A9lestin Matte wrote: > Hello, > > Apologies, patch sent in previous email of this thread is incorrect. > Please find correct patch attached. > > In fact, the pgarchives repository is in a weird state, in which the > migration adding two tables is missing > (0005_apiclient_threadsubscription.py when running makemigrations). My > guess is that this is because these tables use SERIALs, which django does > not handle properly, and must by created using raw SQL. Am I right? > Is it something that should be fixed? > Ugfh, yeah that one is really embarrassing on my part, and I thought I'd cleaned that one up but clearly not. The whole threadsubscription part wasn't finished, and was not supposed to be included in 4d159ca8b4efb0b1cf0893bca63d6e9489a9095f. The correct solution there is to revert most of 4d159ca8b4efb0b1cf0893bca63d6e9489a9095f, to have it include only the parts that are supposed to be there. And then reapply them at some time in the future when the code is finished. I'll go clean that up -- thanks for bringing my attention back to that! --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000aed30b05cf05f947 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Oct 22, 2021 at 5:20 PM C=C3= =A9lestin Matte <celestin.ma= tte@cmatte.me> wrote:
Hello,

Apologies, patch sent in previous email of this thread is incorrect. Please= find correct patch attached.

In fact, the pgarchives repository is in a weird state, in which the migrat= ion adding two tables is missing (0005_apiclient_threadsubscription.py when= running makemigrations). My guess is that this is because these tables use= SERIALs, which django does not handle properly, and must by created using = raw SQL. Am I right?
Is it something that should be fixed?

U= gfh, yeah that one is really embarrassing=C2=A0on my part, and I thought I&= #39;d cleaned that one up but clearly not. The whole threadsubscription=C2= =A0part wasn't finished, and was not supposed to be included in=C2=A04d= 159ca8b4efb0b1cf0893bca63d6e9489a9095f.=C2=A0

The = correct solution there is to revert most of=C2=A04d159ca8b4efb0b1cf0893bca6= 3d6e9489a9095f, to have it include only the parts that are supposed to be t= here. And then reapply them at some time in the future when the code is fin= ished. I'll go clean that up -- thanks for bringing my attention back t= o that!
=C2=A0
--
--000000000000aed30b05cf05f947--