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 1lvU8c-000320-TZ for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Jun 2021 00:19:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lvU8b-0000Rt-JB for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Jun 2021 00:19:33 +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 1lvU8b-0000Rl-6X for pgsql-hackers@lists.postgresql.org; Tue, 22 Jun 2021 00:19:33 +0000 Received: from mail-io1-xd32.google.com ([2607:f8b0:4864:20::d32]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lvU8Y-0006Hn-5f for pgsql-hackers@postgresql.org; Tue, 22 Jun 2021 00:19:31 +0000 Received: by mail-io1-xd32.google.com with SMTP id b7so1524778ioq.12 for ; Mon, 21 Jun 2021 17:19:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Nv8EieVq7ovrSCD0HnY3dAiCZYlB6oDdZjWOkhs4+Aw=; b=bLkd0ysXmmKxRj8+Z9bv7haw4Xi5WTRhbCmiw2aPyIL1j6DaSKpxqPXYecwwrNpbqR TcD/8Xre7fGhodQvCqeMOdruL7pWSN0vOXkdB0MsSujnjbnCPKLAm9IqxCzImMIXynMF +fdYN+yCfXmYYk/KKK/Q+Z616aGRfXP6UqHR21kjBkUvhRAZxVxGlS1db1yPXiwTjwd7 w7WY/eCdv+iLmFjiqAUUdX8v8CxqPsZspOUNvELlUqdE3qHJVArxJnoOegzTCup3xw3o +xQhullWKE4T9WnCjKEhZDkLS85D2q8HJv819K5u04x4fWTkjsTQz2c3Tf544w8S1SX+ PzmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Nv8EieVq7ovrSCD0HnY3dAiCZYlB6oDdZjWOkhs4+Aw=; b=t0YAwZ7QY+UhzXnHYE5YyVp/JdsQusHtCl7NogDaYokMNos9DtRmfd70VvntGkOn0h 2mH3LM0H4A9uUUkuWU4LhUglrEF9S3ZQ3lFLWZOaQZddvlt5HLPvYghujOQ8Sjh+S74A NaA01jEiVSBgZstV8LZQk478vW+aUdio7BzMQ/+ijmO+U7ZBgIQ4BPQnkcvycJHdXf4x 7bCewGq8KjcxuqAYgHQxPW4CbWOKgq+FV2Vtvv+r82fM5cgp20M7P7+5bDxg0krgt98c nZ4C5dZk+A7ZgYo2c6ASVZxoh+fCCR/IwnsrV+42ieXVinUCDJ2yIPyLjoFDk8gBjzeJ 1WWA== X-Gm-Message-State: AOAM530MVUUTTjWp7BTJxBRCTiG6xAs01n7fQnXI0KbvqhYUW7t4/e27 gDivvJ6K/dg3RTC5vx9CN0/SWQ== X-Google-Smtp-Source: ABdhPJzhe4BLOqhZ+kivHQ9jvl1sJTJpHi+NKMiMW41c4fRenStM/NmnMZ3hN3tC0maWQjVKi1rUyA== X-Received: by 2002:a6b:4419:: with SMTP id r25mr508036ioa.205.1624321169069; Mon, 21 Jun 2021 17:19:29 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id e2sm8807425iot.50.2021.06.21.17.19.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Jun 2021 17:19:28 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 8376C800A3B; Mon, 21 Jun 2021 19:19:27 -0500 (CDT) Date: Mon, 21 Jun 2021 19:19:27 -0500 From: Justin Pryzby To: Michael Paquier Cc: Andrey Borodin , Peter Eisentraut , Heikki Linnakangas , pgsql-hackers@postgresql.org, Thomas Munro , Peter Geoghegan , Andres Freund Subject: Re: Different compression methods for FPI Message-ID: <20210622001927.GE29179@telsasoft.com> References: <20210615161456.GP31772@telsasoft.com> <74CD8839-05DD-40F5-9609-58B79AD2151E@yandex-team.ru> <5C10FAD9-DC15-45E5-BCF9-B179A1ABA82E@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Jun 22, 2021 at 09:11:26AM +0900, Michael Paquier wrote: > On Sun, Jun 20, 2021 at 11:15:08PM +0500, Andrey Borodin wrote: > > I have some small questions. > > > > 1. > > + report_invalid_record(record, "image at %X/%X compressed with %s not supported, block %d", > > + (uint32) (record->ReadRecPtr >> 32), > > + (uint32) record->ReadRecPtr, > > + "lz4", > > + block_id); > > Can we point out to user that the problem is in the build? > > What about the following error then? Say: > "image at %X/%X compressed with LZ4 not supported by build, block > %d". The two similar, existing messages are: +#define NO_LZ4_SUPPORT() \ + ereport(ERROR, \ + (errcode(ERRCODE_FEATURE_NOT_SUPPORTED), \ + errmsg("unsupported LZ4 compression method"), \ + errdetail("This functionality requires the server to be built with lz4 support."), \ + errhint("You need to rebuild PostgreSQL using --with-lz4."))) src/bin/pg_dump/pg_backup_archiver.c: fatal("cannot restore from compressed archive (compression not supported in this installation)"); src/bin/pg_dump/pg_backup_archiver.c: pg_log_warning("archive is compressed, but this installation does not support compression -- no data will be available"); src/bin/pg_dump/pg_dump.c: pg_log_warning("requested compression not available in this installation -- archive will be uncompressed"); -- Justin