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 1nnGnr-0001Pd-5H for pgsql-www@arkaria.postgresql.org; Sat, 07 May 2022 09:32:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nnGnn-00008i-RT for pgsql-www@arkaria.postgresql.org; Sat, 07 May 2022 09:32:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnGnn-00008Z-KI for pgsql-www@lists.postgresql.org; Sat, 07 May 2022 09:32:39 +0000 Received: from imap2.cmatte.me ([54.37.205.152]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnGnk-0002UO-Pb for pgsql-www@lists.postgresql.org; Sat, 07 May 2022 09:32:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cmatte.me; s=myselector; t=1651915954; bh=oE+LY1cv7E3YYMKgHK0t71GhybW5Wi/LnzzjzykUcFg=; h=Date:Subject:To:References:From:In-Reply-To; b=e45ANnpvLLG2gfLOfWALFrqtFp7P3s7TsWW/cFRr0pekYEmuGk3Y7vHh/2FMd089Q fZ3akpHiD0Rf3g2aQCX6GiwvgbJ3HlkVYSbbajilhzFhJOpp3VNRgA5obtyv8lRP80 YZc9RGY0FcdmGIvgVSCHTnA04iv8SOoFveUL5riDGvLraOT1iigrinZTlMOWg/5j50 Ur5jfVvat0DTRUE8DrC9+i5ij5dFBhbbvoFNH3eRHRaaxwwuLKwKpQFowKOzDwoYWe tq21sAFuM73fPxuYIHioLuytcNvPwLgiBiu2/n3lesJv9r/HTT2Fch+uiwrEPpPvzC 0jwpGl6nACM8w== Message-ID: Date: Sat, 7 May 2022 11:32:33 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCHES] pgarchives: merge schema.sql into Django's model Content-Language: en-US To: pgsql-www@lists.postgresql.org, Magnus Hagander References: <12eb75f0-3fc2-14f3-0931-4f29e145f182@cmatte.me> From: =?UTF-8?Q?C=c3=a9lestin_Matte?= In-Reply-To: <12eb75f0-3fc2-14f3-0931-4f29e145f182@cmatte.me> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi there, Gentle reminder that this patch has not been reviewed and may have been forgotten On 03/02/2022 14:30, Célestin Matte wrote: > As discussed in previous threads before [1, 2], database creations file are currently split between the Django model and a SQL file. Discrepancy in the database's definition exists between them. As a consequence, the database cannot be created easily. > This series of patches merge schema.sql into Django's model, and adds specific postgres components that cannot be handled by Django's ORM using RunSQL() in a migration file. > > Please also note that I integrated several other patches to avoid multiple migration files: > - I allowed message.parentid to be null, as discussed in [1]. This can cause Internal Server Errors in views.py, which are fixed by the second patch. > - I used BinaryFields for bytea columns (message.rawtxt and attachments.attachment), which seems to be the way to integrate bytea into Django > > It may be a good opportunity to remove all mentions of pg_dict, pg_stop and associated file. I'm not sure of the consequences of this. According to [2], these are the remains of an aborted idea. > Also, what does tsparer bring? Can the installation of pgarchives be simplified by replacing it with pg_catalog.english? > > > [1]: https://www.postgresql.org/message-id/CABUevEyFpYPEHh0AAyTAsgymRKOOVA1SY_pDHPCbBQQ9BawfTA%40mail.gmail.com > [2]: https://www.postgresql.org/message-id/CABUevEy_i1xAKscMv4KZ0%3DbE8050bBcQfWaNyjwZZBofZx7JgQ%40mail.gmail.com -- Célestin Matte