Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tAE5r-00ES6H-Fj for pgsql-performance@arkaria.postgresql.org; Sun, 10 Nov 2024 19:59:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tAE5o-008cnt-SW for pgsql-performance@arkaria.postgresql.org; Sun, 10 Nov 2024 19:59:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tAE5o-008cnk-I4 for pgsql-performance@lists.postgresql.org; Sun, 10 Nov 2024 19:59:29 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tAE5m-001B7n-Lq for pgsql-performance@lists.postgresql.org; Sun, 10 Nov 2024 19:59:27 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-28893cc3acdso520268fac.2 for ; Sun, 10 Nov 2024 11:59:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1731268766; x=1731873566; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=8SmlK0QkqT3ULkqvmaOEnteXRB5QJr9BvgMz8DD0iQo=; b=W1KsDnXffB6o7a3s8qbUTB6QHuXvNXAZ5cWHPmqEVR+R0HfTmpqyrmJC55LGlp6FKt XXdP4qJ//cGPbJA2anU4F5nDyck6xZwQX9GbuRnx/YtBZvgEFJsQ3lKZGCQI37Vwxlch 4ZORzkr4uNEgGzAv6O2RdyMbC9Hu+QsDC6QgKzWa1gJU3ghKP/iEu9IGD0Nsf3Meitxz 4OQTMg+ydIo6l4hly8LAqT7A+FxiPHQ0EoqUkdKiFIG2WzBl2enRsAHw+sgyzQDwSd1h WT2uEXYnE+nibGI4OeKa/9dyHSEqFLowzhnJdOGtTQQionvrgMiDoqLpHpSQctkGWVej F9uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731268766; x=1731873566; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=8SmlK0QkqT3ULkqvmaOEnteXRB5QJr9BvgMz8DD0iQo=; b=fPsI1d+QRjnKJdiiC5Mst2OGy7hhqqEq13OPcmKKjP4xQg3iPRBxDGkKQR8+2AVU2N RyGPcU8ubY2PO4Y9F77z7dPd1m7+kcTqRluS/s5wM8ro1WZoaRGIcZrsA7NX7wJnyyNq I7RpJwU7TM7AOa+jP6lGOIW0ZBjwVfHxOtsLGbIxafXxFOrgNLmWbX4qD/UegD4OslnT 0+AycC6t8L4ZBODVf39r3Q+p3CtKqLFvy16ZIsGjT2HJ1Q09o3VaCp5I7midygmKds2x 41jaCvy+nGeC/4ZXyHlKud281g/P3KdTrbK5RhflP1tgP8+wRsxeQI0kG8+l5nfT0X0e rbKA== X-Gm-Message-State: AOJu0YyI1GfTC5XsNcM/SbhtKclpLcWYwfqBoM8AB90/XR0yWhBEb7hC T79hBi9KAXT9rfyS5yutcJqmEuaQHMpB58uzUTHLGgi5uRzQqA1mAct/Dkc7MZSURFiv0xKmDa8 pzH3aB64Yp0NRh74A1nUbMJCbqTg= X-Google-Smtp-Source: AGHT+IEmR0hLJOn5L1hWEbxw9uQvZs1kQi2WXZ5I4gcjKE+XnGB+E00oVN8xOP8H6QZnkO6FhkAeCUCDi+dzzM0KZNY= X-Received: by 2002:a05:6870:7f11:b0:27b:5ac1:6aca with SMTP id 586e51a60fabf-2955fc9aeaamr2028106fac.0.1731268765886; Sun, 10 Nov 2024 11:59:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Thomas Munro Date: Mon, 11 Nov 2024 08:58:49 +1300 Message-ID: Subject: Re: Performance of Query 4 on TPC-DS Benchmark To: Ba Jinsheng Cc: "pgsql-performance@lists.postgresql.org" , "lepihov@gmail.com" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Nov 11, 2024 at 8:36=E2=80=AFAM Ba Jinsheng = wrote: > The default configurations of PostgreSQL incur the error: "ERROR: could = not resize shared memory segment "/PostgreSQL.3539600020" to 2097152 bytes:= No space left on device" No comment on your optimiser experiments for now, but for this error: it reminds me of a low/default --shm-size limit from Docker, or other similar container stuff?