Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1irr69-0003bF-MY for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2020 22:25:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1irr66-0000QQ-K9 for pgsql-docs@arkaria.postgresql.org; Wed, 15 Jan 2020 22:25:10 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1irr66-0000QJ-7b for pgsql-docs@lists.postgresql.org; Wed, 15 Jan 2020 22:25:10 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1irr63-0005bS-0a for pgsql-docs@lists.postgresql.org; Wed, 15 Jan 2020 22:25:09 +0000 Received: by mail-wr1-x441.google.com with SMTP id j42so17236593wrj.12 for ; Wed, 15 Jan 2020 14:25:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=MsA2BsulZ0VnNtnAkmFcZt5fLVS7eqmbeapUUaCBxzs=; b=Dcvhqr0O/Bcqa1C8mwSMuPWwZb19vjjsghRMOUG1gn+DbGjuwAlR7sRwARK15O0+Tq TBYoCx9oO1QtINBe5NJklTWBWjr7KojqOdQcUiHU69tu0Gw9DXIYFfOmdvfJ4WUoxbqL A3hutKCiqsSmrKtODexcv1jjGtartbe6vKNNKb+Qjwr/E+FlGtyRXMXotkmW4raBOhue 61b677NPJmANvmYo0qcNWXDHudj2TEi4rkb3Crst4qqn8ZvH/iSZ06j9ZQLm9mMFviXt uwwc3c22MV7hIlyeHrcWioLkv7luBFoXBdb6ia7M5cnBQppK4nQ5Bzm2rt4SSBm4S//C 2YWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=MsA2BsulZ0VnNtnAkmFcZt5fLVS7eqmbeapUUaCBxzs=; b=mze0xgYYOm7zOV2PPjQKY0vyo/u1irly6cQz4apFOHhf38f6EDxrMyzbp2hCNn6M8K u1i9xhL+ZZS04RvArkmx38ra/Vp2mHxNuC94RDLlEcjRZjaMi9RoywBTE5pY1y5nnMox ccpUCCFEeFGYx2HL39gKKTP+bnOPHJnV01reFOJTTV5IhcvZ78rWG9a7Ds9VWuyqdJB+ rii68GWjXvmdtZuS0WDu8qOJcAMpybQODO6wZqwdTeK7hJRHyqaBcWihg2c2EhYSLd7n qm04yu1S8U7LD6lvQ38MoJ57azQ9IDa094fTf2MCcqE8UHWYZL7dumYyblBjqTYIN3z2 jlXA== X-Gm-Message-State: APjAAAVzhVFgIB2IBppRfajqXk4FVPvkQEZB37CdQ4A9u2u0Qd63Fp37 hnYCQA/e+tl4TLAEXgUqFbiJgBW+JLQ= X-Google-Smtp-Source: APXvYqzYQfN4c66gTZWuDu79I+nKFDoFB+uPwBK6O4SlPzAyJo1x+iU4BT/1AT9xx3dHh8d8vrZkYg== X-Received: by 2002:a5d:608e:: with SMTP id w14mr34482131wrt.256.1579127104709; Wed, 15 Jan 2020 14:25:04 -0800 (PST) Received: from localhost.localdomain (pd95690bc.dip0.t-ipconnect.de. [217.86.144.188]) by smtp.gmail.com with ESMTPSA id m21sm1747975wmi.27.2020.01.15.14.25.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jan 2020 14:25:04 -0800 (PST) Message-ID: Subject: Re: Shrinking SVG (Again) From: Laurenz Albe To: =?ISO-8859-1?Q?J=FCrgen?= Purtz , pgsql-docs@lists.postgresql.org Date: Wed, 15 Jan 2020 23:25:00 +0100 In-Reply-To: <1246dec7-7426-6d5c-94a0-13ecd052b9fc@purtz.de> References: <1246dec7-7426-6d5c-94a0-13ecd052b9fc@purtz.de> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 2020-01-15 at 14:56 +0100, Jürgen Purtz wrote: > I plan to deliver 3 more graphics, see attachment. When creating their > textual description in the SGML files I faced a problems: The patch of > GSoD > https://www.postgresql.org/message-id/flat/CAEkD-mBFQb61gHNWR0cN5K4G4q-i1PRwNn_OKVkKSaaJa5_LbA%40mail.gmail.com#67104a6097e63371c527b14ff43ddafb > is not yet committed. But this chapter is a good place for the graphics. > Will the GSoD patch become part of the documentation? Both Tom and me showed interest, and the feedback was that some things could be improved. I have not heard back from the author since; I hope she didn't get discouraged. There were definitely some things there that shouldn't go to waste. > Any comments? Errors in the graphics? Suggestions? What's about the GSoD > patch? I particularly like the first image with the memory and process architecture. Some mistakes: - wal_buffers is shared memory, but it is not a part of shared_buffers - The process that performs most of the writes to the data files is the checkpointer. Sometimes backends also have to write to data files. Minor quibbles: - The "server process" is traditionally called "backend process" - "Special purpose memory" is strange. I thing "private memory" would be better. I don't know how it could be depicted that each of the backends has his own. I liked the "cluster / database / schema" image less. Some problems: - No user data should be stored in the "postgres" database. - "template0" has *no* other schemas or tables. It must be absolutely empty. - I am missing the global objects like roles and tablespaces "outside" the databases. I am fine with the directory layout image, but I wonder what "fluctuating states" may be. Yours, Laurenz Albe