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 1l5F2Q-00083S-An for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Jan 2021 21:41:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l5F2O-0005AR-UB for pgsql-bugs@arkaria.postgresql.org; Thu, 28 Jan 2021 21:41:12 +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 1l5DqM-0000uQ-4f for pgsql-bugs@lists.postgresql.org; Thu, 28 Jan 2021 20:24:42 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l5DqI-0005jW-Bp for pgsql-bugs@lists.postgresql.org; Thu, 28 Jan 2021 20:24:41 +0000 Received: by mail-lj1-x229.google.com with SMTP id m22so525654ljj.4 for ; Thu, 28 Jan 2021 12:24:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=8NGvRFYv02YmBDRIgnErVRC0KYx9Lzzwq7OsBrRf34Y=; b=A0HnjIxVquNZRO2JeFmvVcdMe0w4jTsOzRorqTBC8y8gQmfa1BIDddfZjSo5nqaJ4V YtP/kchcK65ijgW5sCSN6Nhj+Qa6ItJIUwIKitq2Xw3v39cpgabk2HDNvtQzenGVEk/k YMyTIh/KB/AMt5L2TKNC33Keh8tPdajaIv0n41y8eaP8/uwWDFHjLrfa85O848+DdBnI T94Y7dJF/pKvzodiWyuHbX2ULF56Rh4xr6sjpPAF2VbuGjYZHGr54a1IbMP6Lu2S4JDZ a/QPAA9Su33TBzMIlEtxG2hbiJ/yR9N5dS9HVCwThjZsjKYUqU3rIHBVT5VxTbGxnFEM efmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=8NGvRFYv02YmBDRIgnErVRC0KYx9Lzzwq7OsBrRf34Y=; b=Ta1Xw/tsHJ7vGs7VFcOtYWH+T4jlO7N+vi2FaQPru5hMM/bBLhJmoHoRnLINyOp70Z UUWpqRqcC2LSkA50Rj4jQLHMpES+kYF/PkM+Y4AuWRTlWSGqIpcVHrmHTP9opMvXwHqP dj6l8VjKBgYEaswLtdBiu95ln3LSPobvWvMcK90EEDbsQUj0ibvAjPzoMeab+cqoexsr dkVoyzh0vb0wJyHTFFeePXMImKRzvRxb7iu0EupKMfJHNhVMChvdSxuC30+TGSV2Ui8Y RgW3/wCP4Vlq1B+q3EY5dQWJ4/mISYQoGaKCvKxg6LD5OBnwftiUFi7QpshKdSL+DrIO gAjQ== X-Gm-Message-State: AOAM530ihtZc0VtSfBfnIiaytk3kQh0XPgcFH9/BM4iXJ3/jJ1P6gGuN e8IwxcHPMTwAEtOmj4n8dtCezO+JQO8= X-Google-Smtp-Source: ABdhPJxnVfmfcp8fXsTDnN2FaKmeA6j4w34pX3VUddPA4rnM4yH8xT5rlWXweYck1sbO87LloBzMMg== X-Received: by 2002:a2e:8584:: with SMTP id b4mr547913lji.213.1611865476982; Thu, 28 Jan 2021 12:24:36 -0800 (PST) Received: from ?IPv6:2a02:aa1:100f:410:1586:d1b3:6d2c:df25? ([2a02:aa1:100f:410:1586:d1b3:6d2c:df25]) by smtp.gmail.com with ESMTPSA id x19sm1791031lfr.144.2021.01.28.12.24.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Jan 2021 12:24:35 -0800 (PST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: =?utf-8?Q?Tomas_Dalebj=C3=B6rk?= Mime-Version: 1.0 (1.0) Subject: Re: BUG #16842: pg_dump uses seek calls on pipe files: suggesting adding a flag to disable seek calls Date: Thu, 28 Jan 2021 21:24:34 +0100 Message-Id: <3EA55F53-7E84-4F6B-9043-D4DFA7184830@gmail.com> References: <2546666.1611847966@sss.pgh.pa.us> Cc: pgsql-bugs@lists.postgresql.org In-Reply-To: <2546666.1611847966@sss.pgh.pa.us> To: Tom Lane X-Mailer: iPhone Mail (17G80) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk thanks for the feedback Tom is the seek enabled only if =E2=80=94format=3Dcustom or is it enabled regardless of which flag used? regards Tomas Sent from my iPhone > On 28 Jan 2021, at 16:32, Tom Lane wrote: >=20 > =EF=BB=BFPG Bug reporting form writes: >> It would be good to add a flag to disable this feature, as some devices d= oes >> not support seek calls, for example streaming devices such as a tape >> drive. >=20 > That seems like an extremely niche use-case, so I'm unexcited about adding= > a switch for it. You can get the same results with a pipe, as your quoted= > response from Red Hat support suggests. >=20 > Note that disabling seeking is not all that desirable in the first place, > as it will result (for -Fc output) in a dump file that is significantly > restrictive to restore performance, due to lack of data offset pointers. > You might really be best advised to rethink whether you want to write > directly to an unseekable device, rather than to a temp file you transfer > to tape later. >=20 > regards, tom lane