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 1sVxCM-00CUSJ-RP for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 17:51:46 +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 1sVxCK-0057Pn-RU for pgsql-general@arkaria.postgresql.org; Mon, 22 Jul 2024 17:51:45 +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 1sVxCK-0057Pe-FO for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 17:51:44 +0000 Received: from mail-vk1-xa30.google.com ([2607:f8b0:4864:20::a30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sVxCI-000vGZ-Qw for pgsql-general@lists.postgresql.org; Mon, 22 Jul 2024 17:51:44 +0000 Received: by mail-vk1-xa30.google.com with SMTP id 71dfb90a1353d-4f53081ef0eso214799e0c.2 for ; Mon, 22 Jul 2024 10:51:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721670701; x=1722275501; 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=5+cVbCd7FPsLiYFDXoGLiaI45/B9IuT9MqiOsVlvkUY=; b=Jq7XjJOm7aBqCBS2oDuF8Y/VCREp1YcAKgcopkMQ6zuKCynw83Y0cgTGyjf6FawGg4 XftvQt3mvTXv8wteb30GcUWuFgL1lb5DKJ4lMdtH9TebdcCHQ2OW7u0lv4UKHryfS/iS g0GT0N/1tF3sH7iJcBYKPnap7d3HHDWONVEYv7Tf4LCUkMmSd3BcBlERavacOJkWh6ll VjF40swXxsYFj5c2KgiSpH83cXNF0JzFAUNxL7B3/Iq3ABlsESLFSdsY265fY7v5HZ1U ZihwS2Ku5PVX/X8hgeM9ygaK83s5bEk2JXDfpcagGX932l3v/s8nlGO4oQWV0VqIwVMi rpIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721670701; x=1722275501; 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=5+cVbCd7FPsLiYFDXoGLiaI45/B9IuT9MqiOsVlvkUY=; b=JuY11T+1KTNBtGhkUaTbqF2XssYGHkiiCufnhqCfrv/KL5EkHiH4BxRHKq/CBTd5kq gQbVgSI8u6zyK4Tbwivx23BXGRDkFnNJPAUrr17QWMFPGH4xTcrlB/feJfyRAuy2zSeZ DrCgVzLavo0at5ao49BH39XF1Ay1Gj1Pbf7KU4ptgOfpQX8doBZONlwR097v96oA8jnZ dOdmWnqz8E4MYH/ZMBuWp+lVoSNoQMl+batWvA1cdKBTcgZh6F1f+4HXuVHVCW+IR/JB MM0E5EnbESTIM9k+UyCywW5BjfH7mFU6kw5f2X9nnvkHfOW7tG8hxjK3aB5L13bGJPA/ Xr4Q== X-Gm-Message-State: AOJu0YxqEPAKKIa1fvOFdX+gWIf5K5XWJEQnhqHD3CFZ5jv+EChLWSfZ FHjPeg6ZwcYezTKlN3bnlnE3pGq7ylJZId3prE7r9xlso9ZRwKbAqTSxhez1Uw7dOf/rb3NC+iF f0/4nbpw4ix3zp8J2b6TberJA08HjwgXNjkM= X-Google-Smtp-Source: AGHT+IEg899O1oN4RCs88s5C4aR4C03r5m28A1gqDc6MLRlzB7Lq8TVQgzhqua96f9Ta4Zq5GrFpQSVytGEKZj2jUWc= X-Received: by 2002:a05:6122:1ad5:b0:4ef:594a:a706 with SMTP id 71dfb90a1353d-4f506873a3cmr9317461e0c.14.1721670700988; Mon, 22 Jul 2024 10:51:40 -0700 (PDT) MIME-Version: 1.0 References: <80c9b0ea-c874-40ad-a006-fb1eb37464c2@aklaver.com> <44b44ece-dce6-4b4f-b751-8787a5a071e0@aklaver.com> <011a5254-4abb-460b-bd02-92e8dfc0e5ea@aklaver.com> <9cc12221-ba75-4ba0-803f-51be5c8f1525@aklaver.com> <4c21a115-ec58-4e79-86b8-8626bd307e02@aklaver.com> In-Reply-To: <4c21a115-ec58-4e79-86b8-8626bd307e02@aklaver.com> From: =?UTF-8?B?RXJ0YW4gS8O8w6fDvGtvZ2x1?= Date: Mon, 22 Jul 2024 20:51:30 +0300 Message-ID: Subject: Re: Windows installation problem at post-install step To: Adrian Klaver Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000008d7fbf061dd9b237" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008d7fbf061dd9b237 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Adrian Klaver , 22 Tem 2024 Pzt, 20:37 tarihinde =C5=9Funu yazd=C4=B1: > What is the command you use to restore the pg_dumpall file? > within psql I run \i template1 should not be dropped in the pg_dumpall file. > > Is there output that shows that happening? > -- -- Databases -- -- -- Database "template1" dump -- -- -- PostgreSQL database dump -- -- Dumped from database version 16.3 -- Dumped by pg_dump version 16.3 SET statement_timeout =3D 0; SET lock_timeout =3D 0; SET idle_in_transaction_session_timeout =3D 0; SET client_encoding =3D 'UTF8'; SET standard_conforming_strings =3D on; SELECT pg_catalog.set_config('search_path', '', false); SET check_function_bodies =3D false; SET xmloption =3D content; SET client_min_messages =3D warning; SET row_security =3D off; UPDATE pg_catalog.pg_database SET datistemplate =3D false WHERE datname =3D 'template1'; DROP DATABASE template1; -- -- Name: template1; Type: DATABASE; Schema: -; Owner: postgres -- CREATE DATABASE template1 WITH TEMPLATE =3D template0 ENCODING =3D 'UTF8' LOCALE_PROVIDER =3D libc LOCALE =3D 'Turkish_Turkey.1254'; Above lines are taken from the dump file itself and it does indeed drop the template1. I think this is because this is a cluster dump. Later it tries to create a new template1 and that command causes an error because of Windows locale name. > Was template1 dropped in the Windows Postgres instance? > No. It still is there. BTW dump is taken using the below command line on Windows system. "C:\Program Files\PostgreSQL\16\bin\pg_dumpall.exe" -U postgres -h 127.0.0.1 -p 5432 -c -f "c:\yedek\cluster.dump.sql" Thanks & Regards, Ertan --0000000000008d7fbf061dd9b237 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Adrian Klaver <adrian.klaver@aklaver.com>, 22 Tem 2024 Pzt, 2= 0:37 tarihinde =C5=9Funu yazd=C4=B1:
What is the command you use= to restore the pg_dumpall file?

within= psql I run \i <dump_file_name>=C2=A0

template1 should not be dropped in the pg_dumpall file.

Is there output that shows that happening?

-= -
-- Databases
--

--
-- Database "template1" dump=
--

--
-- PostgreSQL database dump
--

-- Dumped from= database version 16.3
-- Dumped by pg_dump version 16.3

SET stat= ement_timeout =3D 0;
SET lock_timeout =3D 0;
SET idle_in_transaction_= session_timeout =3D 0;
SET client_encoding =3D 'UTF8';
SET st= andard_conforming_strings =3D on;
SELECT pg_catalog.set_config('sear= ch_path', '', false);
SET check_function_bodies =3D false;SET xmloption =3D content;
SET client_min_messages =3D warning;
SET= row_security =3D off;

UPDATE pg_catalog.pg_database SET datistempla= te =3D false WHERE datname =3D 'template1';
DROP DATABASE templa= te1;
--
-- Name: template1; Type: DATABASE; Schema: -; Owner: postgre= s
--

CREATE DATABASE template1 WITH TEMPLATE =3D template0 ENCODI= NG =3D 'UTF8' LOCALE_PROVIDER =3D libc LOCALE =3D 'Turkish_Turk= ey.1254';

Above lines are taken from the dump fi= le itself and it does indeed drop the template1. I think this is because th= is is a cluster dump.
Later it tries to create a new template1 an= d that command causes an error because of Windows locale name.

Was template1 dropped in the Windows Postgres instance?

No. It still is there.

BTW dump i= s taken using the below command line on Windows system.
"C:\= Program Files\PostgreSQL\16\bin\pg_dumpall.exe" -U postgres -h 127.0.0= .1 -p 5432 -c -f "c:\yedek\cluster.dump.sql"

Thanks & Regards,
Ertan
--0000000000008d7fbf061dd9b237--