postgresql-17.0-1 Application - silent installation Issue

On 11/10/24 07:11, JOLAPARA Urvi (SAFRAN) wrote:

C2 - Confidential

Hello Team,

I am from Application Packaging team. we have created the package of
PostgreSQL 17.0-1 Application.

You are going to need to provide more detail on the package creation
process.

We have used the command line parameter for installation is this :
*“postgresql-17.0-1-windows-x64.exe--mode unattended --unattendedmodeui
none --optionfile C:\Temp\Install”*

This is working in English language machine but it is failing in French
language machine and throwing below error:

You should provide error messages as text not as image, so folks can run
them through a translator if need be.

erreur d'ecriture du fichier -> file write error

according to Google.

we tried giving permission to this folder, then we have used

Which directory(folder) would that be?

*“--installer-launage fr”* parameter *“--locale fr”* parameters but

Should that not be --installer-language?

Also shouldn't this:

--locale fr

be?:

--locale fr-FR

still not working.

Please assist to resolve the issue asap.

Thanks & Regards,

Urvi Jolapara

urvi.jolapara@safrangroup.com <mailto:urvi.jolapara@safrangroup.com>

Image

*www.safran-group.com* <http://www.safran-group.com/fr/&gt;

#
" Ce courriel et les documents qui lui sont joints peuvent contenir des
informations confidentielles, être soumis aux règlementations relatives
au contrôle des exportations ou ayant un caractère privé. S'ils ne vous
sont pas destinés, nous vous signalons qu'il est strictement interdit de
les divulguer, de les reproduire ou d'en utiliser de quelque manière que
ce soit le contenu. Toute exportation ou réexportation non autorisée est
interdite Si ce message vous a été transmis par erreur, merci d'en
informer l'expéditeur et de supprimer immédiatement de votre système
informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or
proprietary information and may be subject to export control laws and
regulations. If you are not the intended recipient, you are notified
that any dissemination, copying of this e-mail and any attachments
thereto or use of their contents by any means whatsoever is strictly
prohibited. Unauthorized export or re-export is prohibited. If you have
received this e-mail in error, please advise the sender immediately and
delete this e-mail and all attached documents from your computer system."
#

--
Adrian Klaver
adrian.klaver@aklaver.com

C2 - Confidential

Hello Klaver,

We are using PSADT for creating a script and installing through SCCM.
And when we are installing Through Software center it is throwing error as below:

"There has been an error
error while writing file C:\windows\Temp\postgresql_installer_8b85d458af\temp_check_comspec.bat"

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

www.safran-group.com

-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Monday, November 11, 2024 9:49 PM
To: JOLAPARA Urvi (SAFRAN) <urvi.jolapara@safrangroup.com>; pgsql-general@postgresql.org
Cc: KRISHNAN LINGATHAR Karupaswamy (SAFRAN) <karupaswamy.krishnan-lingathar@safrangroup.com>
Subject: Re: postgresql-17.0-1 Application - silent installation Issue

CAUTION: This message originated from an outside organization. In case of suspicion, click on "Report to SAFRAN Security" from the Outlook ribbon.

On 11/10/24 07:11, JOLAPARA Urvi (SAFRAN) wrote:

C2 - Confidential

Hello Team,

I am from Application Packaging team. we have created the package of
PostgreSQL 17.0-1 Application.

You are going to need to provide more detail on the package creation process.

We have used the command line parameter for installation is this :
*“postgresql-17.0-1-windows-x64.exe--mode unattended
--unattendedmodeui none --optionfile C:\Temp\Install”*

This is working in English language machine but it is failing in
French language machine and throwing below error:

You should provide error messages as text not as image, so folks can run them through a translator if need be.

erreur d'ecriture du fichier -> file write error

according to Google.

we tried giving permission to this folder, then we have used

Which directory(folder) would that be?

*“--installer-launage fr”* parameter *“--locale fr”* parameters but

Should that not be --installer-language?

Also shouldn't this:

--locale fr

be?:

--locale fr-FR

still not working.

Please assist to resolve the issue asap.

Thanks & Regards,

Urvi Jolapara

urvi.jolapara@safrangroup.com <mailto:urvi.jolapara@safrangroup.com>

Image

*www.safran-group.com*
<https://urldefense.com/v3/__http://www.safran-group.com/fr/__;!!P3ITo
RM6tg!lcu8B2WYC3q9sLuzLhCkS5OgLIQrDrJR_oXes8Pd-fyTKP6hFQEEp-cnYrUJTMFp
brUMR5UjNRKPgmKfoJ8RWMAgLSunLtYk$ >

#
" Ce courriel et les documents qui lui sont joints peuvent contenir
des informations confidentielles, être soumis aux règlementations
relatives au contrôle des exportations ou ayant un caractère privé.
S'ils ne vous sont pas destinés, nous vous signalons qu'il est
strictement interdit de les divulguer, de les reproduire ou d'en
utiliser de quelque manière que ce soit le contenu. Toute exportation
ou réexportation non autorisée est interdite Si ce message vous a été
transmis par erreur, merci d'en informer l'expéditeur et de supprimer
immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or
proprietary information and may be subject to export control laws and
regulations. If you are not the intended recipient, you are notified
that any dissemination, copying of this e-mail and any attachments
thereto or use of their contents by any means whatsoever is strictly
prohibited. Unauthorized export or re-export is prohibited. If you
have received this e-mail in error, please advise the sender
immediately and delete this e-mail and all attached documents from your computer system."
#

--
Adrian Klaver
adrian.klaver@aklaver.com

#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles, être soumis aux règlementations relatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorized export or re-export is prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#

On 11/11/24 22:09, JOLAPARA Urvi (SAFRAN) wrote:

C2 - Confidential

This is a publicly readable list, the above has no meaning in that context.

Hello Klaver,

We are using PSADT for creating a script and installing through SCCM.

1) I don't work with Windows so I have no idea what the above
means.

2) You did not answer the rest of the questions I asked in my previous post.

a) "we tried giving permission to this folder, then we have used"

Which directory(folder) would that be?

b) ' *“--installer-launage fr”* parameter *“--locale fr”* parameters but
...'

Should that not be --installer-language?

Also shouldn't this:

--locale fr

be?:

--locale fr-FR

And when we are installing Through Software center it is throwing error as below:

"There has been an error
error while writing file C:\windows\Temp\postgresql_installer_8b85d458af\temp_check_comspec.bat"

I would suggest looking in the Windows system log to see if it provides
more information for the above error.

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

www.safran-group.com

--
Adrian Klaver
adrian.klaver@aklaver.com

C2 - Confidential

Hello Klaver,

I have added below the log where setup is failing on FR language machine.

Log started 11/14/2024 at 09:04:33
Preferred installation mode : unattended
Trying to init installer in mode unattended
Mode unattended successfully initialized
Setting variable whoami from C:\WINDOWS\System32\whoami
Script exit code: 0

Script output:
autorite nt\système

Script stderr:

Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Base Directory. Setting variable iBaseDirectory to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Branding. Setting variable iBranding to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Version. Setting variable brandingVer to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Shortcuts. Setting variable iShortcut to empty value
[09:04:35] Using branding: PostgreSQL 17
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 SB_Version. Setting variable sb_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 pgAdmin_Version. Setting variable pgadmin_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 CLT_Version. Setting variable clt_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Data Directory. Setting variable server_data_dir to empty value
Erreur d'écriture du fichier C:/Windows/Temp/postgresql_installer_ee9259ae9d/temp_check_comspec.bat
Exiting with code 1

The Parameters which you suggested in last mail also not working with PostgresSQL exe.

Please transfer the request who works with windows. We need the solution asap.

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

www.safran-group.com

-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Tuesday, November 12, 2024 10:06 PM
To: JOLAPARA Urvi (SAFRAN) <urvi.jolapara@safrangroup.com>; pgsql-general@postgresql.org
Cc: KRISHNAN LINGATHAR Karupaswamy (SAFRAN) <karupaswamy.krishnan-lingathar@safrangroup.com>
Subject: Re: postgresql-17.0-1 Application - silent installation Issue

CAUTION: This message originated from an outside organization. In case of suspicion, click on "Report to SAFRAN Security" from the Outlook ribbon.

On 11/11/24 22:09, JOLAPARA Urvi (SAFRAN) wrote:

C2 - Confidential

This is a publicly readable list, the above has no meaning in that context.

Hello Klaver,

We are using PSADT for creating a script and installing through SCCM.

1) I don't work with Windows so I have no idea what the above means.

2) You did not answer the rest of the questions I asked in my previous post.

a) "we tried giving permission to this folder, then we have used"

Which directory(folder) would that be?

b) ' *“--installer-launage fr”* parameter *“--locale fr”* parameters but ...'

Should that not be --installer-language?

Also shouldn't this:

--locale fr

be?:

--locale fr-FR

And when we are installing Through Software center it is throwing error as below:

"There has been an error
error while writing file C:\windows\Temp\postgresql_installer_8b85d458af\temp_check_comspec.bat"

I would suggest looking in the Windows system log to see if it provides more information for the above error.

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

https://urldefense.com/v3/__http://www.safran-group.com__;!!P3IToRM6tg
!i7_r9jHMtJfM4PYV1cyvZR9mQYp6lntjOt9T-GA9pRPIUtgmhYYAOML3XIg9yKfkczYXx
mYTan6MAGcfZ9TX8oUAU_sEIeqE$

--
Adrian Klaver
adrian.klaver@aklaver.com

#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations confidentielles, être soumis aux règlementations relatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque manière que ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été transmis par erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary information and may be subject to export control laws and regulations. If you are not the intended recipient, you are notified that any dissemination, copying of this e-mail and any attachments thereto or use of their contents by any means whatsoever is strictly prohibited. Unauthorized export or re-export is prohibited. If you have received this e-mail in error, please advise the sender immediately and delete this e-mail and all attached documents from your computer system."
#

Please transfer the request who works with windows. We need the solution asap.

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

If a windows admin/user shows up they may be better able to help. There is no one to "transfer" to.
The list of missing keys suggests to me that the installation didn't do go well. Whose installer did you use?

On 11/14/24 01:05, JOLAPARA Urvi (SAFRAN) wrote:

C2 - Confidential

Hello Klaver,

I have added below the log where setup is failing on FR language machine.

Log started 11/14/2024 at 09:04:33
Preferred installation mode : unattended
Trying to init installer in mode unattended
Mode unattended successfully initialized
Setting variable whoami from C:\WINDOWS\System32\whoami
Script exit code: 0

Script output:
autorite nt\système

Script stderr:

Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Base Directory. Setting variable iBaseDirectory to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Branding. Setting variable iBranding to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Version. Setting variable brandingVer to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Shortcuts. Setting variable iShortcut to empty value
[09:04:35] Using branding: PostgreSQL 17
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 SB_Version. Setting variable sb_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 pgAdmin_Version. Setting variable pgadmin_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 CLT_Version. Setting variable clt_version to empty value
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Data Directory. Setting variable server_data_dir to empty value
Erreur d'écriture du fichier C:/Windows/Temp/postgresql_installer_ee9259ae9d/temp_check_comspec.bat
Exiting with code 1

The Parameters which you suggested in last mail also not working with PostgresSQL exe.

Please transfer the request who works with windows. We need the solution asap.

Then you probably need to contact a paid tech support company who deals
with Windows and Postgres. This is the Postgres mailing list and Windows
support is not really something you will find here.

Thanks & Regards,
Urvi Jolapara
urvi.jolapara@safrangroup.com

www.safran-group.com

-----Original Message-----

--
Adrian Klaver
adrian.klaver@aklaver.com

 Team
Need exact SQL query to find List of Detach Partitioned Tables (Yet to be Dropped)
The following is the query which i used, i am using and i found an bug which is listing an newly created table (last week)
SELECT relnamespace::regnamespace::text AS schema_name, relname AS table_name
FROM   pg_class c
WHERE  NOT relispartition  -- !
AND    relkind = 'r' and lower(relnamespace::regnamespace::text) not in ('pg_catalog','partman','information_schema')  and
lower(relnamespace::regnamespace::text) in ('XYZ')
order by  relnamespace::regnamespace::text, relname ;

On Fri, Nov 15, 2024 at 12:46 PM Bharani SV-forum <esteembsv-forum@yahoo.com>
wrote:

Need exact SQL query to find List of Detach Partitioned Tables (Yet to be
Dropped)

The premise that a detached table is distinguishable from any other table
that is not a partition is an interesting one that I wouldn't necessarily
expect to be determinable. You could probably write a query listing tables
that are candidates for attaching to an existing partitioned table and then
filter out those that are actually attached.

David J.

On 11/15/24 11:46, Bharani SV-forum wrote:

 Team

Need exact SQL query to find List of Detach Partitioned Tables (Yet to
be Dropped)

The following is the query which i used, i am using and i found an bug
which is listing an newly created table (last week)

As David G. Johnston said how would you know it was formally a partition?:

https://www.postgresql.org/docs/current/sql-altertable.html

"
DETACH PARTITION partition_name [ CONCURRENTLY | FINALIZE ]

This form detaches the specified partition of the target table. The
detached partition continues to exist as a standalone table, but no
longer has any ties to the table from which it was detached.

[...]
"

The only I could see this working is if you had a standard naming scheme
for partitions and then you could do a regex search in pg_class for that
pattern where relkind = 'r'.

SELECT relnamespace::regnamespace::text AS schema_name, relname AS
table_name
FROM   pg_class c
WHERE  NOT relispartition  -- !
AND    relkind = 'r' and lower(relnamespace::regnamespace::text) not in
('pg_catalog','partman','information_schema')  and
lower(relnamespace::regnamespace::text) in ('XYZ')
order by  relnamespace::regnamespace::text, relname ;

--
Adrian Klaver
adrian.klaver@aklaver.com

TeamPl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X

Env = EC2 based Community PostgreSQL Ver 13.16.2

we will be performing upgrade of our EC2 server too along with new OS.
Need help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X
 ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2- ensure to capture all the pre.req meant for ver 15.10 are being met.
- shutdown db.- take offline full backup (PG_DATA folder alone)  using OS command
Proposed-new EC2 server (with new Operating System version along Postgres Ver 15.10 Binaries)- install postgres 15.10 binaries- ensure to DISABLE auto startup and shutdown of postgres 15.10-  Restore offline full backup (PG_DATA folder alone) using OS command
-  start performing pg_upgrade step to upgrade postgres from ver 13.16.2 to 15.10
please guide me, if i have missed any steps in the abovesaid process

To start new DB features, planning to rollout out the following feature's alone
a) TLE extension for password complianceb) parallelize vacuum jobs to utilize -j option

On 12/2/24 14:18, Bharani SV-forum wrote:

Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver
15.X

Env = EC2 based Community PostgreSQL Ver 13.16.2

we will be performing upgrade of our EC2 server too along with new OS.

Need help in vetting my steps for Postgres DB upgrade from Ver 13.X to
ver 15.X
*ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
- ensure to capture all the pre.req meant for ver 15.10 are being met.
- shutdown db.
- take offline full backup (PG_DATA folder alone)  using OS command

*Proposed-new EC2 server (with new Operating System version along
Postgres Ver 15.10 Binaries)*
- install postgres 15.10 binaries
- ensure to DISABLE auto startup and shutdown of postgres 15.10
-  Restore offline full backup (PG_DATA folder alone) using OS command
-  start performing pg_upgrade step to upgrade postgres from ver 13.16.2

This is not going to work, you need to have Postgres 13 installed also.

It all laid out here:

https://www.postgresql.org/docs/15/pgupgrade.html

In Usage section.

to 15.10

please guide me, if i have missed any steps in the abovesaid process

To start new DB features, planning to rollout out the following
feature's alone
a) TLE extension for password compliance
b) parallelize vacuum jobs to utilize -j option

--
Adrian Klaver
adrian.klaver@aklaver.com

On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum <esteembsv-forum@yahoo.com>
wrote:

Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver
15.X

Env = EC2 based Community PostgreSQL Ver 13.16.2

we will be performing upgrade of our EC2 server too along with new OS.

Need help in vetting my steps for Postgres DB upgrade from Ver 13.X to
ver 15.X

*ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
- ensure to capture all the pre.req meant for ver 15.10 are being met.
- shutdown db.
- take offline full backup (PG_DATA folder alone) using OS command

*Proposed-new EC2 server (with new Operating System version along Postgres
Ver 15.10 Binaries)*
- install postgres 15.10 binaries
- ensure to DISABLE auto startup and shutdown of postgres 15.10
- Restore offline full backup (PG_DATA folder alone) using OS command
- start performing pg_upgrade step to upgrade postgres from ver 13.16.2
to 15.10

please guide me, if i have missed any steps in the abovesaid process

To start new DB features, planning to rollout out the following feature's
alone
a) TLE extension for password compliance
b) parallelize vacuum jobs to utilize -j option

To migrate from one server to another while upgrading, one must use
pg_dump/pg_restore OR Logical Replication.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

On 12/2/24 14:31, Ron Johnson wrote:

On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
<esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>> wrote:

Team
Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
ver 15.X

Env = EC2 based Community PostgreSQL Ver 13.16.2

we will be performing upgrade of our EC2 server too along with new OS.

Need help in vetting my steps for Postgres DB upgrade from Ver 13.X
to ver 15.X
*ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
- ensure to capture all the pre.req meant for ver 15.10 are being met.
- shutdown db.
- take offline full backup (PG_DATA folder alone)  using OS command

*Proposed-new EC2 server (with new Operating System version along
Postgres Ver 15.10 Binaries)*
- install postgres 15.10 binaries
- ensure to DISABLE auto startup and shutdown of postgres 15.10
-  Restore offline full backup (PG_DATA folder alone) using OS command
-  start performing pg_upgrade step to upgrade postgres from ver
13.16.2 to 15.10

please guide me, if i have missed any steps in the abovesaid process

To start new DB features, planning to rollout out the following
feature's alone
a) TLE extension for password compliance
b) parallelize vacuum jobs to utilize -j option

To migrate from one server to another while upgrading, one must use
pg_dump/pg_restore OR Logical Replication.

Really?

Then this:

https://www.postgresql.org/docs/current/pgupgrade.html

must be random nose.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--
Adrian Klaver
adrian.klaver@aklaver.com

On 12/2/24 14:46, Adrian Klaver wrote:

On 12/2/24 14:31, Ron Johnson wrote:

On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
<esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>> wrote:

    Team
    Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
    ver 15.X

    Env = EC2 based Community PostgreSQL Ver 13.16.2

    we will be performing upgrade of our EC2 server too along with new
OS.

    Need help in vetting my steps for Postgres DB upgrade from Ver 13.X
    to ver 15.X
    *ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
    - ensure to capture all the pre.req meant for ver 15.10 are being
met.
    - shutdown db.
    - take offline full backup (PG_DATA folder alone)  using OS command

    *Proposed-new EC2 server (with new Operating System version along
    Postgres Ver 15.10 Binaries)*
    - install postgres 15.10 binaries
    - ensure to DISABLE auto startup and shutdown of postgres 15.10
    -  Restore offline full backup (PG_DATA folder alone) using OS
command
    -  start performing pg_upgrade step to upgrade postgres from ver
    13.16.2 to 15.10

    please guide me, if i have missed any steps in the abovesaid process

    To start new DB features, planning to rollout out the following
    feature's alone
    a) TLE extension for password compliance
    b) parallelize vacuum jobs to utilize -j option

To migrate from one server to another while upgrading, one must use
pg_dump/pg_restore OR Logical Replication.

Really?

Then this:

https://www.postgresql.org/docs/current/pgupgrade.html

must be random nose.

Oh yeah, that was smooth.

Second attempt:

... must be random noise.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--
Adrian Klaver
adrian.klaver@aklaver.com

Ron/AdrianThanks for your input.Your suggestion is
option#1 ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*-  ensure to capture all the pre.req meant for ver 15.10 are being  met.
     - enable logical replication tagged to proposed new EC2 server (with newer Higher OS Version ).

Proposed-new EC2 server (with new Operating System version along
    Postgres Ver 13.16.2 and 15.10 Binaries)*     - install postgres 13.16.2 binaries
    - have postgres setup on par with existing setup and having proper logical replication 
    - install postgres 15.10 binaries     - ensure to DISABLE auto startup and shutdown of postgres 13.16.2
      - ensure to DISABLE auto startup and shutdown of postgres 15.10    - start postgres db ver 13.16.2 and ensure all are good. no errors in postgres log file
    -  start performing pg_upgrade step to upgrade postgres from ver 13.16.2 to 15.10
pl Vet the newer steps (revised version).

RegardsBharani
On Monday, December 2, 2024 at 05:48:19 PM EST, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 12/2/24 14:46, Adrian Klaver wrote:

On 12/2/24 14:31, Ron Johnson wrote:

On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
<esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>> wrote:

    Team
    Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
    ver 15.X

    Env = EC2 based Community PostgreSQL Ver 13.16.2

    we will be performing upgrade of our EC2 server too along with new
OS.

    Need help in vetting my steps for Postgres DB upgrade from Ver 13.X
    to ver 15.X
    *ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
    - ensure to capture all the pre.req meant for ver 15.10 are being
met.
    - shutdown db.
    - take offline full backup (PG_DATA folder alone)  using OS command

    *Proposed-new EC2 server (with new Operating System version along
    Postgres Ver 15.10 Binaries)*
    - install postgres 15.10 binaries
    - ensure to DISABLE auto startup and shutdown of postgres 15.10
    -  Restore offline full backup (PG_DATA folder alone) using OS
command
    -  start performing pg_upgrade step to upgrade postgres from ver
    13.16.2 to 15.10

    please guide me, if i have missed any steps in the abovesaid process

    To start new DB features, planning to rollout out the following
    feature's alone
    a) TLE extension for password compliance
    b) parallelize vacuum jobs to utilize -j option

To migrate from one server to another while upgrading, one must use
pg_dump/pg_restore OR Logical Replication.

Really?

Then this:

https://www.postgresql.org/docs/current/pgupgrade.html

must be random nose.

Oh yeah, that was smooth.

Second attempt:

... must be random noise.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--
Adrian Klaver
adrian.klaver@aklaver.com

On 12/2/24 15:41, Bharani SV-forum wrote:

Ron/Adrian
Thanks for your input.
Your suggestion is

*option#1*
 ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
-  ensure to capture all the pre.req meant for ver 15.10 are being  met.
     - enable logical replication tagged to proposed new EC2 server

No, logical replication != pg_upgrade process.

(with newer Higher OS Version ).

Proposed-new EC2 server (with new Operating System version along
    Postgres Ver 13.16.2 and 15.10 Binaries)*
     - install postgres 13.16.2 binaries
    - have postgres setup on par with existing setup and having proper
logical replication

Again, no.

    - install postgres 15.10 binaries
     - ensure to DISABLE auto startup and shutdown of postgres 13.16.2
      - ensure to DISABLE auto startup and shutdown of postgres 15.10
    - start postgres db ver 13.16.2 and ensure all are good. no errors
in postgres log file
    -  start performing pg_upgrade step to upgrade postgres from ver
13.16.2 to 15.10

pl Vet the newer steps (revised version).

I don't know how much clearer it can be, follow the step by step
instructions shown here:

https://www.postgresql.org/docs/current/pgupgrade.html

"These are the steps to perform an upgrade with pg_upgrade:

[...]

"

Regards
Bharani

On Monday, December 2, 2024 at 05:48:19 PM EST, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:

On 12/2/24 14:46, Adrian Klaver wrote:

On 12/2/24 14:31, Ron Johnson wrote:

On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
<esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>

<mailto:esteembsv-forum@yahoo.com>> wrote:

    Team
    Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
    ver 15.X

    Env = EC2 based Community PostgreSQL Ver 13.16.2

    we will be performing upgrade of our EC2 server too along with new
OS.

    Need help in vetting my steps for Postgres DB upgrade from Ver 13.X
    to ver 15.X
    *ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
    - ensure to capture all the pre.req meant for ver 15.10 are being
met.
    - shutdown db.
    - take offline full backup (PG_DATA folder alone)  using OS command

    *Proposed-new EC2 server (with new Operating System version along
    Postgres Ver 15.10 Binaries)*
    - install postgres 15.10 binaries
    - ensure to DISABLE auto startup and shutdown of postgres 15.10
    -  Restore offline full backup (PG_DATA folder alone) using OS
command
    -  start performing pg_upgrade step to upgrade postgres from ver
    13.16.2 to 15.10

    please guide me, if i have missed any steps in the abovesaid process

    To start new DB features, planning to rollout out the following
    feature's alone
    a) TLE extension for password compliance
    b) parallelize vacuum jobs to utilize -j option

To migrate from one server to another while upgrading, one must use
pg_dump/pg_restore OR Logical Replication.

Really?

Then this:

https://www.postgresql.org/docs/current/pgupgrade.html

<https://www.postgresql.org/docs/current/pgupgrade.html&gt;

must be random nose.

Oh yeah, that was smooth.

Second attempt:

... must be random noise.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>

--
Adrian Klaver
adrian.klaver@aklaver.com

Adrian
Proposed new Server is intended to have higher OS Version (centos ver 9.0) and higher Postgres Version 15.10
Does logical replication will have issues , if the existing asis server is having Postgres ver 13.16.2 with Cent Os 7.0 with the new server having higher OS version Centos Ver 9.0 and then propose to have the Postgres to be upgraded from ver 13.16.2 to 15.10
Hope u have understood my question
On Monday, December 2, 2024 at 06:47:10 PM EST, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 12/2/24 15:41, Bharani SV-forum wrote:

Ron/Adrian
Thanks for your input.
Your suggestion is

*option#1*
   ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
-  ensure to capture all the pre.req meant for ver 15.10 are being  met.
       - enable logical replication tagged to proposed new EC2 server

No, logical replication != pg_upgrade process.

(with newer Higher OS Version ).

Proposed-new EC2 server (with new Operating System version along
      Postgres Ver 13.16.2 and 15.10 Binaries)*
       - install postgres 13.16.2 binaries
      - have postgres setup on par with existing setup and having proper
logical replication

Again, no.

      - install postgres 15.10 binaries
       - ensure to DISABLE auto startup and shutdown of postgres 13.16.2
        - ensure to DISABLE auto startup and shutdown of postgres 15.10
      - start postgres db ver 13.16.2 and ensure all are good. no errors
in postgres log file
      -  start performing pg_upgrade step to upgrade postgres from ver
13.16.2 to 15.10

pl Vet the newer steps (revised version).

I don't know how much clearer it can be, follow the step by step
instructions shown here:

https://www.postgresql.org/docs/current/pgupgrade.html

"These are the steps to perform an upgrade with pg_upgrade:

[...]

"

Regards
Bharani

On Monday, December 2, 2024 at 05:48:19 PM EST, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:

On 12/2/24 14:46, Adrian Klaver wrote:
  > On 12/2/24 14:31, Ron Johnson wrote:
  >> On Mon, Dec 2, 2024 at 5:18 PM Bharani SV-forum
  >> <esteembsv-forum@yahoo.com <mailto:esteembsv-forum@yahoo.com>
<mailto:esteembsv-forum@yahoo.com>> wrote:
  >>
  >>     Team
  >>     Pl Help in vetting my steps for Postgres DB upgrade from Ver 13.X to
  >>     ver 15.X
  >>
  >>     Env = EC2 based Community PostgreSQL Ver 13.16.2
  >>
  >>     we will be performing upgrade of our EC2 server too along with new
  >> OS.
  >>
  >>     Need help in vetting my steps for Postgres DB upgrade from Ver 13.X
  >>     to ver 15.X
  >>     *ASIS-existing server = EC2 with Community PostgreSQL Ver 13.16.2*
  >>     - ensure to capture all the pre.req meant for ver 15.10 are being
  >> met.
  >>     - shutdown db.
  >>     - take offline full backup (PG_DATA folder alone)  using OS command
  >>
  >>     *Proposed-new EC2 server (with new Operating System version along
  >>     Postgres Ver 15.10 Binaries)*
  >>     - install postgres 15.10 binaries
  >>     - ensure to DISABLE auto startup and shutdown of postgres 15.10
  >>     -  Restore offline full backup (PG_DATA folder alone) using OS
  >> command
  >>     -  start performing pg_upgrade step to upgrade postgres from ver
  >>     13.16.2 to 15.10
  >>
  >>     please guide me, if i have missed any steps in the abovesaid process
  >>
  >>     To start new DB features, planning to rollout out the following
  >>     feature's alone
  >>     a) TLE extension for password compliance
  >>     b) parallelize vacuum jobs to utilize -j option
  >>
  >>
  >> To migrate from one server to another while upgrading, one must use
  >> pg_dump/pg_restore OR Logical Replication.
  >
  > Really?
  >
  > Then this:
  >
  > https://www.postgresql.org/docs/current/pgupgrade.html
<https://www.postgresql.org/docs/current/pgupgrade.html&gt;
  >
  > must be random nose.

Oh yeah, that was smooth.

Second attempt:

... must be random noise.

  >
  >>
  >> --
  >> Death to <Redacted>, and butter sauce.
  >> Don't boil me, I'm still alive.
  >> <Redacted> lobster!
  >

--
Adrian Klaver
adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>

--
Adrian Klaver
adrian.klaver@aklaver.com

On 12/2/24 15:52, Bharani SV-forum wrote:

Adrian

Proposed new Server is intended to have higher OS Version (centos ver
9.0) and higher Postgres Version 15.10

Alright I did not catch this " ... with new OS" from your original post.
I saw "Take offline full backup (PG_DATA folder alone) using OS
command" and "Restore offline full backup (PG_DATA folder alone) using
OS command" and assumed like to like on the OS, my mistake.

Does logical replication will have issues , if the existing asis server
is having Postgres ver 13.16.2 with Cent Os 7.0
with the new server having higher OS version Centos Ver 9.0 and then
propose to have the Postgres to be upgraded
from ver 13.16.2 to 15.10

Logical replication would not have issue with this as that is one of
it's use cases. The question now becomes whether that is the quickest/
most efficient way to do this.

That depends on:

1) What is the size of database(s) you are dealing with?

2) What sort of downtime can you afford?

3) EC2 --> EC2, are they the same region?

Hope u have understood my question

On Monday, December 2, 2024 at 06:47:10 PM EST, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:

--
Adrian Klaver
adrian.klaver@aklaver.com

AdrianNoted about, Logical replication would not have issue with this as that is one of
it's use cases.

qsn1: What is the size of database(s) you are dealing with?
ans1: roughly 25 GB  (maximum size)

qsn2 : What sort of downtime can you afford?
ans2: can be maximum 30 mins or so
qsn3: EC2 --> EC2, are they the same region?ans3: Right Question. I assume the same region
Can you pl provide your insight now 
On Monday, December 2, 2024 at 07:20:52 PM EST, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

On 12/2/24 15:52, Bharani SV-forum wrote:

Adrian

Proposed new Server is intended to have higher OS Version (centos ver
9.0) and higher Postgres Version 15.10

Alright I did not catch this " ... with new OS" from your original post.
I saw "Take offline full backup (PG_DATA folder alone)  using OS
command" and "Restore offline full backup (PG_DATA folder alone) using
OS command" and assumed like to like on the OS, my mistake.

Does logical replication will have issues , if the existing asis server
is having Postgres ver 13.16.2 with Cent Os 7.0
with the new server having higher OS version Centos Ver 9.0 and then
propose to have the Postgres to be upgraded
from ver 13.16.2 to 15.10

Logical replication would not have issue with this as that is one of
it's use cases. The question now becomes whether that is the quickest/
most efficient way to do this.

That depends on:

1) What is the size of database(s) you are dealing with?

2) What sort of downtime can you afford?

3) EC2 --> EC2, are they the same region?

Hope u have understood my question

On Monday, December 2, 2024 at 06:47:10 PM EST, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:

--
Adrian Klaver
adrian.klaver@aklaver.com