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.96) (envelope-from ) id 1wHlHI-007UT0-1O for pgsql-general@arkaria.postgresql.org; Tue, 28 Apr 2026 16:27:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wHlHH-000btj-0m for pgsql-general@arkaria.postgresql.org; Tue, 28 Apr 2026 16:27:15 +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.96) (envelope-from ) id 1wHlHF-000bta-3B for pgsql-general@lists.postgresql.org; Tue, 28 Apr 2026 16:27:14 +0000 Received: from fhigh-a4-smtp.messagingengine.com ([103.168.172.155]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wHlHD-00000003DNe-1U5Q for pgsql-general@postgresql.org; Tue, 28 Apr 2026 16:27:12 +0000 Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfhigh.phl.internal (Postfix) with ESMTP id 603EA1400074; Tue, 28 Apr 2026 12:27:10 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Tue, 28 Apr 2026 12:27:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1777393630; x=1777480030; bh=iTqUNT7kaKtxH2l+DR1l2r0icebMOM8Vgucg69EwSfM=; b= QPj/OLOzUN7B90MKB7pEtVjockXTtg9Eouy9TDl7Xg71t5cF09TyBeZBlPB24t/+ fDO7dO5qxcuirOz9ETcsNeijpV3Qa5soGsmfLY9OEIWvdJmP0pZZaq9jB57dpbbT kv0CCad6lOJVg4CfZjugardGqZuWf+ehJpbhEqSSuq4qwqlF4BvEw/P4HavyyvPe jalkUqodlpCH/e3O3gn6x5DHlXpOZd5qIPtHJARC0r4lkZtymKWWKb5K5mzNx2Zy Jfet3aZ1T2oFHIKU9AIJlS4IpQHQw+Pd4aNtuni3dwmW1Z5ZW94NqhU1gEUZN7B+ Wt36yR2kM0/ra88IkUstVg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1777393630; x=1777480030; bh=i TqUNT7kaKtxH2l+DR1l2r0icebMOM8Vgucg69EwSfM=; b=IvIDZF6e+2g1ZRjT+ y3+6vb+QW4PCWkBYr3P4sY+6LdCDaQZwpHkJ+QBPxJl+biSup64+RmkEGhCQxWoB LfDGeX9Wp0HuxFQWmn5XIgCG//PMcliFvHDUYmTnCZmMp0BRBk4rDWYxQFMVvR7c F0beVlUcEuk4TvkmfaBevb3axSQ69WtLx9z4S0g/zJNIewcHdpRB1YXfFdkXRaA3 W1KG2oraTGOUF0HQEpYRgnmz7pHo0dBCRe89yRoAY0LRlb6bfMs6kpG1j2KnebLt ksKSXnxLB+YfM6sYN8ePoJTjwfImnIDvS3u62o1w0rHKKtB5G1XWQ8UbeaesdG8T fl8bQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdekvddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttd dvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghv vghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeffleegieefgfevud ehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheejheenucevlhhushhtvghrufhi iigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrse grkhhlrghvvghrrdgtohhmpdhnsggprhgtphhtthhopedvpdhmohguvgepshhmthhpohhu thdprhgtphhtthhopegufhhgphhoshhtghhrvghsfeesghhmrghilhdrtghomhdprhgtph htthhopehpghhsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 28 Apr 2026 12:27:09 -0400 (EDT) Message-ID: <25e61545-624f-4de3-99c6-47b42d136d2c@aklaver.com> Date: Tue, 28 Apr 2026 09:27:07 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: can recs be transferred between DBs ? To: dfgpostgres , pgsql-general@postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/28/26 8:56 AM, dfgpostgres wrote: > psql (15.3, server 15.15) on linux > > dvdb=# \d arch_restore >                   Table "misc.arch_restore" >  Column |       Type        | Collation | Nullable | Default > --------+-------------------+-----------+----------+--------- >  pk     | integer           |           | not null | >  proj   | character varying |           |          | >  data   | character varying |           |          | > Indexes: >     "arch_restore_pkey" PRIMARY KEY, btree (pk) > > dvdb=# select * from arch_restore order by pk; >  pk | proj  |    data > ----+-------+------------ >   1 | alpha | the_data_1 >   2 | alpha | the_data_2 >   3 | alpha | the_data_3 >   4 | beta  | the_data_4 >   5 | beta  | the_data_5 >   6 | beta  | the_data_6 >   7 | gamma | the_data_7 >   8 | gamma | the_data_8 >   9 | gamma | the_data_9 > (9 rows) > > I decided that it's time to archive the 'beta' project.  So I create a > new DB in the PG instance and put them all there leaving... How did you transfer the data to the new database and could you not use the same process to transfer the beta data back? > > Thanks in Advance