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 1sw3zE-001dY1-5q for pgsql-general@arkaria.postgresql.org; Wed, 02 Oct 2024 18:22:08 +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 1sw3zD-001fJn-FD for pgsql-general@arkaria.postgresql.org; Wed, 02 Oct 2024 18:22:07 +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 1sw3zD-001fJP-3o for pgsql-general@lists.postgresql.org; Wed, 02 Oct 2024 18:22:07 +0000 Received: from mail-oi1-x22b.google.com ([2607:f8b0:4864:20::22b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sw3zA-002Adk-Kl for pgsql-general@lists.postgresql.org; Wed, 02 Oct 2024 18:22:05 +0000 Received: by mail-oi1-x22b.google.com with SMTP id 5614622812f47-3e3991843e2so100083b6e.3 for ; Wed, 02 Oct 2024 11:22:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727893324; x=1728498124; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ceqdcMfGH3O1/4eSyJUIQM8KKAYKe2Btmko1I1Uuea8=; b=FhA/JpzLBz5oipaKMgREZhHD2Qjpge3RxPy/5EN+PP6qSoE1K3sEKglmr+wNkbegj0 ZfX2souAcQ5Ntypvaepd0nOnVuQ+fUU62/8HKR4nQ5hGpCE1QeV/zT2sIuAByD8v16ue gh0xe7NtTklaXA3FfQXzW9NLwJI1rWUGjtcjkJmuw79TL52i/eHm7zS0HfwiFThaEsoY kePlzSa9RVXYGtm2DladMUOQCec78BVWNvyYlpOgWBng6xVrFXaFzyNrTlmuoAxRKSqL BNPY7kv0hGwDFIUxIqP2Oryux1SO3djx2RzqhH7gG9YMLAS5Xyl/ZocyQI7cG/xwPN2k 8gtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727893324; x=1728498124; h=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=ceqdcMfGH3O1/4eSyJUIQM8KKAYKe2Btmko1I1Uuea8=; b=F7Epd+7mYpWUbF/2DHs3rg6t//dXHTkTDqzB1sQjSKRPxBC6AiCVk74eb1tINNNvpG eDJlcd/DoxvITLFDJUBOd7tWpC4H/R39xBtEYin0+Xp9qJfGOZouJYkuqdzLApw2yWzB zzzxcWSYbCbVpS/bqx7aUafT2Uzem1TcXvy0ceJ6YJIWzO/CaJbJEvd1UAkMQBbdNtMw xjC8NVMYqVRcu/9JqQma8kVxaQWRZPb9FH4hzv9X8dshPtROYO9j+jUDrnLbIIDHFsQu 6OVi+NwrCshzMQLGrV1lWba/mkV+QV4FIyfBmXOYtD4y00ejJua7DN+BNOebK0Wpg2eP 5gyw== X-Gm-Message-State: AOJu0Ywy/EcvFaHmei4lyXhPDi+R/g5Q9AkP/OelKGj9NIDOUsOyddOd G6eRGM8/EQuij8ZJh7SJ/r6iEj4kEXge6WUQj0PbEtedsYXr2C3tm/sMM8rbZVpUZGLtOTvbTV2 nElkDo40sRThvhJirbGs+1YMn+uX1EQ== X-Google-Smtp-Source: AGHT+IFMKozGegrJJF1k9kVG2UkgfMfN7l4/r+G4vwMnnMqpvK7Gjz5z325hZ4utDXQhJIla3yW9+FnLEq4LMK41HmI= X-Received: by 2002:a05:6808:210c:b0:3e3:982c:eb2e with SMTP id 5614622812f47-3e3b40e7f52mr4113557b6e.10.1727893324018; Wed, 02 Oct 2024 11:22:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Wed, 2 Oct 2024 11:21:54 -0700 Message-ID: Subject: Re: pg_dump 17 produces files incompatible with older server versions To: Sam Kidman Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c9bcc106238283bd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c9bcc106238283bd Content-Type: text/plain; charset="UTF-8" On Wed, Oct 2, 2024, 11:17 Sam Kidman wrote: > > Unfortunately we use the latest version of the client tools (ie > pg_dump and kin) but we run the same database server version as we use > in production (12) and so now we're unable to import our database > schema with the error below: > You are operating in an unsupported manner and there is no goal to support it, aside from psql. David J. --000000000000c9bcc106238283bd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Oct 2, 2024, 11:17 Sam Kidman <sam@fresho.com> wrote:

Unfortunately we use the latest version of the client tools (ie
pg_dump and kin) but we run the same database server version as we use
in production (12) and so now we're unable to import our database
schema with the error below:
=
You are operating in an unsupported manner and = there is no goal to support it, aside from psql.
David J.

--000000000000c9bcc106238283bd--