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 1t2x3L-008tba-Mm for pgsql-admin@arkaria.postgresql.org; Mon, 21 Oct 2024 18:22:51 +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 1t2x3I-00AFOA-QB for pgsql-admin@arkaria.postgresql.org; Mon, 21 Oct 2024 18:22:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t2x3I-00AFO1-EJ for pgsql-admin@lists.postgresql.org; Mon, 21 Oct 2024 18:22:48 +0000 Received: from mail-lj1-x22e.google.com ([2a00:1450:4864:20::22e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t2x3G-002GRC-Lo for pgsql-admin@postgresql.org; Mon, 21 Oct 2024 18:22:48 +0000 Received: by mail-lj1-x22e.google.com with SMTP id 38308e7fff4ca-2fb6110c8faso48841281fa.1 for ; Mon, 21 Oct 2024 11:22:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729534964; x=1730139764; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=pAs6Ia41u74P4F4fvAT0RCKt79htb16f0hDgUR5D2JY=; b=VSSXK4IfogVxl3ccvIhR3kZu/AI4wj9V3a97p6SWYXUjCBtfKru1Dj3gHTpH4wvvbd eH3sxG2IQjjAu0HcMuzHW3IrnMK5D5frhtWaaHsnT/DEXN6NW5Ib8aSlEjyGVJ+YruGA O9ln/sNiHRYLRs2Lj9wQUhmBpY+LPOzmXSlIMZEUZuabFmALojX9R6rbID8V8UL4fCaO Uz5zcabdmofa0ByAjirkE0tQDFKXfsiKmIDGXxcgQXEGmdofVNFmytv/RMPUTOOL6LLc rgc7jnFJAH8GM+rVq3qC+yuUk74h3OAVczrszt8rYNulfqAR7SXD2xZx0B2xqBGyPXhd OK7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729534964; x=1730139764; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=pAs6Ia41u74P4F4fvAT0RCKt79htb16f0hDgUR5D2JY=; b=Faat/6Bw5UFdL+cjg0R0xLcyp63oTZttty1bznnym8kE+rIoFifu9Y8P6w/B6KVPe+ W+lsJqSAhd4P+tL0HQmJ0V8Cwgok3BRWEaQgZoIt7gt342luiUOiA+YcOYO9D7V9/xD1 0tN4HRLmBvkk7AMcblr1TD3U6owHEFl6yCLb/UWgjjc7GFeWQIp2WK9J8Ec7riHEx5cm pQPCXuu9QqvF2COW5lDVOwNl3plU0X2ErskxzJ+B7aJw+y675JTkwmi2tKgwXckrmSmI XZvWyVdYJKfAB6W6N/k80OXVgd3pNbCKxO1qwrphiWsxwqot+paFsqSDuW+SDu7oU+DJ xF/g== X-Gm-Message-State: AOJu0YwieIIoGpjDdKWzSSMoXq2j/23mYSfJfTRsx53akaAcKMFX9jtK H6NNPYlKUHbRvZWB1okhnIfZSA4OBZhmm4heKqzb9jukJkqeuvL+veIbGx0FfKEXjRCcCjqOJpf TlEaCHPML64nT6eUm+97rVRm8usu/yw== X-Google-Smtp-Source: AGHT+IF0SqiZzho54y3Pvu7jXGJ7Yq2wt7dVx359fSZpEcBMic0deOU8AEL3WIEXHc/h74V9GHa/3Or5u6vhHyWM1II= X-Received: by 2002:a05:651c:210a:b0:2fb:5d8a:4cd3 with SMTP id 38308e7fff4ca-2fb82da45c7mr52403091fa.0.1729534963996; Mon, 21 Oct 2024 11:22:43 -0700 (PDT) MIME-Version: 1.0 From: Ron Watkins Date: Mon, 21 Oct 2024 11:22:07 -0700 Message-ID: Subject: How do dump server wide configuration? To: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary="00000000000027e18e062500bddb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000027e18e062500bddb Content-Type: text/plain; charset="UTF-8" I have been dumping individual databases with the pg_dump command, but a issue has come up where user configs and other data stored at the server level are not being dumped. Is there a way to dump those data as well? -- Ron Watkins, K7DOG 602.743.5272 --00000000000027e18e062500bddb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have been dumping individual databases with the pg_dump = command, but a issue has come up where user configs and other data stored a= t the server level are not being dumped. Is there a way to dump those data = as well?

--
Ron Watkins, K7DOG
602.743.5= 272
--00000000000027e18e062500bddb--