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 1nA7Xn-0005Bw-4d for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Jan 2022 09:46:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nA7Xl-0002Xg-IA for pgsql-bugs@arkaria.postgresql.org; Wed, 19 Jan 2022 09:46:17 +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 1nA7Xl-0002XX-7K for pgsql-bugs@lists.postgresql.org; Wed, 19 Jan 2022 09:46:17 +0000 Received: from mail-pj1-x1032.google.com ([2607:f8b0:4864:20::1032]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nA7Xj-0007xq-3N for pgsql-bugs@lists.postgresql.org; Wed, 19 Jan 2022 09:46:16 +0000 Received: by mail-pj1-x1032.google.com with SMTP id n16-20020a17090a091000b001b46196d572so2108436pjn.5 for ; Wed, 19 Jan 2022 01:46:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=BcbhjSTRksiiSdQjtRD4m+6ZlzAzDu0QArpWX3k6DZg=; b=fzzd57reZKUlgyBFb6gR3RJOhPQxSPNeiEUT3BMv+7nUDjwRXevp7Xo2/ZUCbp5+6D 3X7OiB64Mk85UZIgFhhVY36ODtXZ3BcYnqnUHNzW+KIJJ2dCGGEgBCy25wzyvXNxSNcU TJVNudz52/g4C0znWC39K7j0mMwwwIQu8CJnpKWIOZNnp8Gdp9C1qqt96uprqD52syN8 07SoyJMHsMm509cd1CyszXfMo0o72lE+f1J2ecjEbcxL1HTFKnAs1M9XolWSATZj0u3E yTdCYDau2su0m8/1JO9fFKIb9jbex5EVVovNuM/aXT2cOjKQF/KSaAkSfn0P9RiRWq4N 0hZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=BcbhjSTRksiiSdQjtRD4m+6ZlzAzDu0QArpWX3k6DZg=; b=NeXm2D6unEeqaSyB3wNgeCXF6DlfI0824RAxrEYwjsuc5b2Lbwtkpj7vkSbWeZ7JxG LuX3v8cmw8ESfL0Nw+Dy8uBfaYRetVX5AX6PGcIqROBNEjqoDcbiWQACs/TIV8faGgSL PnSEVMoF5oMwtPFPnqNFKkr0abDfPBbGYJ1qVxDekpIlEU474pz/oBdE8XXKvZk2sR9D RyPGR1A5He5RaM1sR9Lo8V7U1WKsLk0VYkvJJLBVjwP34tToFFP+vvpa6nwAzKLirR3Z Hjs8n3qU5THws7RUdIJm59DCA6SXVNAaEMypVt9xaLUqJiY6ZIfdEUbel6ioVibOygAh +dzw== X-Gm-Message-State: AOAM532xa0vkoH3z9vBZglDl0sVmBYJpB5dGRfQ4loIyrVTy11RcgPrh AMAvd34eX0xnGs6WzulwG8c= X-Google-Smtp-Source: ABdhPJzj361hRaiAaD0BYl5GZA50nyaiCjd2w5zNEo1CAiL9x8Mr4qcQO7KHfbzEiHUCtPSehpN1Lw== X-Received: by 2002:a17:902:c086:b0:14a:6828:388d with SMTP id j6-20020a170902c08600b0014a6828388dmr30986983pld.17.1642585572905; Wed, 19 Jan 2022 01:46:12 -0800 (PST) Received: from jrouhaud (1-171-184-213.dynamic-ip.hinet.net. [1.171.184.213]) by smtp.gmail.com with ESMTPSA id n15sm13798634pfj.15.2022.01.19.01.46.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Jan 2022 01:46:12 -0800 (PST) Date: Wed, 19 Jan 2022 17:46:07 +0800 From: Julien Rouhaud To: RekGRpth Cc: PostgreSQL mailing lists Subject: Re: BUG #17370: shmem lost on segfault Message-ID: <20220119094607.vdsrbseqfpruuiuk@jrouhaud> References: <17370-a42a313cf1589256@postgresql.org> <20220119092828.aiy3sqoa4lwwtm2g@jrouhaud> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On Wed, Jan 19, 2022 at 02:34:13PM +0500, RekGRpth wrote: > Ok, thanks. > > What I should do in this case (postmaster restarts my background > worker and shared memory is lost)? > When I storage in bgw_extra field - everything is ok (with restarting > after segfault), but it size too small. I don't know, and as I said you should ask on -hackers, ideally with a good description of how everything works or a minimal code to reproduce your problem as it's not really clear right now.