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 1otNIJ-0007wW-Nx for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 06:13:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1otNIG-000846-RP for pgsql-general@arkaria.postgresql.org; Fri, 11 Nov 2022 06:13:36 +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 1otNIG-00083x-FE for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 06:13:36 +0000 Received: from mail-pf1-x435.google.com ([2607:f8b0:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1otNIC-00022A-1Z for pgsql-general@lists.postgresql.org; Fri, 11 Nov 2022 06:13:35 +0000 Received: by mail-pf1-x435.google.com with SMTP id k15so4101550pfg.2 for ; Thu, 10 Nov 2022 22:13:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=XGVO96uPeLyTNXu+eTLv6zU9PsvcSAuzLn48FZruvuU=; b=L03OKarqXhz/mmckA/OpiHqJGXBwi93x/nkBrJkCTbLJI/s1shs3Zs0/vNqmR8nYG/ AjTh0cd+O59y1FyIVnSWz/3QbNJauqmPEXtkY1iw72ofophSkPRd+f++okdVjhNvNME0 0INkGn7goOpMoyXgYTf26oR8QsQtEUbzK8sJfvv7gnAUPA6eSt+kBuVXM2caQeXcLH1I p1zMFPZ7uypofNjJW7GzKmAm+aDNVq2XsilUcPVIU+iKSHVDmaMzGsO8AQWx5s3xRqCT L/Zg14z36JyuKnYP5REQeSh0EWA7t62VMw81Tg1z+HiAddFjyWhseYrr2SRfqv9sv8Ag Qb4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=subject:from:to:content-language:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XGVO96uPeLyTNXu+eTLv6zU9PsvcSAuzLn48FZruvuU=; b=T7JLs/FWpYQNzZZKHbFrIbo1c0KuF8cGlnm8cDBa9PGK9qifGrITB7xCH+dAIgKqgr UtvXcEh2o5r3E2+AJyVAou6dau2mKBDypO3XlU3JqozYCXHI8mEK6ASmY7mta3pL+Sjn 7zXLnvZREkDgYi90yZ8+XdnCVChk7SCQbgkCtWdNB/5okqSdP7uI1fvkTAecoUwlTaeh fQDndnTY+c9faMeIZ6YYuirP+we5Z/myvDQycvnADv265oiuHjaR3uZ2984cqQekB3U1 fvw472iiQjWAR+rmJK+KHaE7bvn1PNji38udkb5/fajq7yjDm18WhIg+azhUz5TnogAA 32Jg== X-Gm-Message-State: ANoB5pnJOLBCM4CFm2QnSXhvH8fCAgiIbWoIHOWhPATdc51PebXLfEo4 Yj+gVNkgBcPNwfC3145ddhSBa46T1Zw= X-Google-Smtp-Source: AA0mqf6vB7VWFKkxBIEvcdOmlrtMdSOrSwN38V0o3I4/SJqIltMln9Roy+OA6P6qJ4WDurQ+drs9Kw== X-Received: by 2002:a63:fa18:0:b0:464:3f16:e2b0 with SMTP id y24-20020a63fa18000000b004643f16e2b0mr336103pgh.566.1668147210258; Thu, 10 Nov 2022 22:13:30 -0800 (PST) Received: from [10.128.56.149] ([155.98.131.5]) by smtp.gmail.com with ESMTPSA id d6-20020a170903230600b00181e55d02dcsm766316plh.139.2022.11.10.22.13.29 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Nov 2022 22:13:29 -0800 (PST) Content-Type: multipart/alternative; boundary="------------1IW007G1dE5GN7asFkk8ZwZW" Message-ID: <78d93a34-2215-84bc-4c71-a8336e469dbe@gmail.com> Date: Thu, 10 Nov 2022 23:13:28 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Content-Language: en-CA To: "pgsql-generallists.postgresql.org" From: Rob Sargent Subject: reviving "custom" dump List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------1IW007G1dE5GN7asFkk8ZwZW Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Short version: Does a current version of postgres tolerate ascii dumps from older versions? I've been charged with reviving an old project.  I have a dump dated July of 2021 which file tells me is a "PostgreSQL custom database dump V1.13-0".  If our compute centre won't roll me a V12(?) postgres server, I'll need to use an "office" machine to bring this dataset back to life.  If I pull that off can I make an ascii dump and import that into our main db server (V14) or will I have to also install V14 in the office and dump/restore with that? --------------1IW007G1dE5GN7asFkk8ZwZW Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Short version: Does a current version of postgres tolerate ascii dumps from older versions?

I've been charged with reviving an old project.  I have a dump dated July of 2021 which file tells me is a "PostgreSQL custom database dump V1.13-0".  If our compute centre won't roll me a V12(?) postgres server, I'll need to use an "office" machine to bring this dataset back to life.  If I pull that off can I make an ascii dump and import that into our main db server (V14) or will I have to also install V14 in the office and dump/restore with that?

--------------1IW007G1dE5GN7asFkk8ZwZW--