Thread: Re: 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/>
> 
> #
> " 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èglementationsrelatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés,
nousvous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque
manièreque ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été
transmispar erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce
courrielainsi 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
exportcontrol laws and regulations. If you are not the intended recipient, you are notified that any dissemination,
copyingof 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
senderimmediately 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.
Settingvariable iBaseDirectory to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Branding. Setting
variableiBranding to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Version. Setting
variablebrandingVer to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Shortcuts. Setting
variableiShortcut 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
variablesb_version to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 pgAdmin_Version.
Settingvariable pgadmin_version to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 CLT_Version. Setting
variableclt_version to empty value
 
Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Data Directory.
Settingvariable 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èglementationsrelatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés,
nousvous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque
manièreque ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été
transmispar erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce
courrielainsi 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
exportcontrol laws and regulations. If you are not the intended recipient, you are notified that any dissemination,
copyingof 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
senderimmediately 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?


> 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èglementationsrelatives au contrôle des exportations ou ayant un caractère privé. S'ils ne vous sont pas destinés,
nousvous signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en utiliser de quelque
manièreque ce soit le contenu. Toute exportation ou réexportation non autorisée est interdite Si ce message vous a été
transmispar erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système informatique ce
courrielainsi 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
exportcontrol laws and regulations. If you are not the intended recipient, you are notified that any dissemination,
copyingof 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
senderimmediately and delete this e-mail and all attached documents from your computer system." 
> #

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.
Settingvariable iBaseDirectory to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Branding. Setting
variableiBranding to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Version. Setting
variablebrandingVer to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Shortcuts. Setting
variableiShortcut 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.
Settingvariable sb_version to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 pgAdmin_Version.
Settingvariable pgadmin_version to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 CLT_Version.
Settingvariable clt_version to empty value
 
> Could not find registry key HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-x64-17 Data Directory.
Settingvariable 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

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

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 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

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>
>  >
>  > 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

On 12/2/24 17:23, Ron Johnson wrote:
> Adrian,
> 
> OP is moving to a new VM when migrating to PG 15.  When was the 
> "cross-server" feature added to pg_upgrade?
> 

Moving to a new VM was not the issue, my mistake was thinking the OS 
version was staying the same.

Then:

On old VM:

"take offline full backup (PG_DATA folder alone)  using OS command"

On new VM:
"Restore offline full backup (PG_DATA folder alone) using OS command"

Followed by installing new Postgres version could be dealt with using 
pg_upgrade. Once I was corrected on what was actually going on then 
doing a dump/restore or logical replication became better choices.


-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/4/24 04:42, Bharani SV-forum wrote:
> Team /Ron/Adrian
> 
> Wann to reconfirm
> we have an setup with
> 
> new server will be with
> 
> will be following the following suggestion
> 
> *On old VM* [ existing server with OS "Amazon Linux release 2 (Karoo) " 
> present in aws "us-east-1 region" and along with postgresql ver 13.16.2  
> - community edn ]
> 
>   - "take offline full backup (PG_DATA folder alone)  using OS command"
> 
> *On new VM [OS "Amazon Linux 2023 " in aws region=us-east-1 and intended 
> db as "postgresql 15.10 - community edn" ] *
> 
>   - "Restore offline full backup (PG_DATA folder alone) using OS command"
> - create postgres unix userid
> - install postgresql ver 15.10 binaries
> - setup respective env variable to point correctly for PG_DATA
> - will follow "pg_upgrade"

That will not work as you would need an install of Postgres 13 on the 
new machine as well. And then there is the issue that the OS version 
changed as well. That would cause issues. Follow the process Greg Sabino 
Mullane posted.

> 
> 
> my question is
> a) is the above said steps is correct with the given existing and 
> proposed setup
> b) is their any known issues using "cross over using pg_upgrade " option 
> between the server's having below said operating system
> *- source = existing server with OS = *Amazon Linux release 2 (Karoo) " 
> present in aws "us-east-1 region" and along with postgresql ver 13.16.2  
> - community edn
> vs
> target - different server *OS "Amazon Linux 2023 " in aws 
> region=us-east-1 and intended db as "postgresql 15.10 - community edn"*
> *
> *
> *
> *
> On Tuesday, December 3, 2024 at 12:28:58 AM EST, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 12/2/24 17:23, Ron Johnson wrote:
>  > Adrian,
>  >
>  > OP is moving to a new VM when migrating to PG 15.  When was the
>  > "cross-server" feature added to pg_upgrade?
>  >
> 
> Moving to a new VM was not the issue, my mistake was thinking the OS
> version was staying the same.
> 
> Then:
> 
> On old VM:
> 
> "take offline full backup (PG_DATA folder alone)  using OS command"
> 
> On new VM:
> "Restore offline full backup (PG_DATA folder alone) using OS command"
> 
> Followed by installing new Postgres version could be dealt with using
> pg_upgrade. Once I was corrected on what was actually going on then
> doing a dump/restore or logical replication became better choices.
> 
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/11/24 11:12, Bharani SV-forum wrote:
> Team
> As suggested from old server, post shutdown of DB, I did OS level dump 
> of PG_DATA folder and had restored in the new server.

If you follow the process shown here:

https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg%40mail.gmail.com

You would not have to do the below.

> 
> Any idea on how to install the older binary postgres 13.18 ( OS=Amazon 
> Linux 2023.6.20241121) under a dedicated folder suffixed as the 
> following e.g.) /usr/pgsql1318
> 
> System Admin had already installed newer version pgsql 15.08 binaries in 
> the  new server (OS= Amazon Linux 2023.6.20241121) in the folder "/usr/bin/"
> 
> We were quoted , OS = Amazon Linux 2023.6.20241121 doesnot support 
> postgres ver 15.10 (Community edition) under its AWS-EC2.

That does not reflect well on Amazon Linux, that it is missing two 
critical bug releases.

> 
> Regards
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/16/24 13:19, Bharani SV-forum wrote:
> Team
> I am getting the following error.
> 
> pg_dump: error: error reading large object 2113418:
> 
> pg_dump: error: could not open large object 3391830:

What user are you running pg_dump as?

What version of pg_dump?

> 
> I tried to give this command DB name = abcefg
> 
> ALTER DATABASE abcefgd SET lo_compat_privileges=on;
> 
> and reran and once again , i am getting the same error
> 
> while doing using psql/pg_dump from old version server running 13.18 [ 
> OS = Amazon Linux release 2 (Karoo) ].

It is either psql or pg_dump. psql is the CLI client for the Postgres 
server. If you are using psql as an alias for Postgres(sql), don't,  it 
only adds confusion.

> 
> Will be pg_dump and pg_restore to restore in the new VM with new OS [OS= 
> amazon linux 2023] and new DB bin pgsql ver 15.09.
> 
> We were told by AWS team, in the new VM tagged OS [OS= amazon linux 
> 2023] , pgsql Ver 13.16 is not supported

Not sure why? It still a community supported version and will be through 
November 2025.

> 
> *I cross checked*
> SELECT oid, count(*)  FROM pg_largeobject_metadata group by oid order by 
> oid ;
> Rows =  4260170 rows
> 
> Can you suggest
> 
> 
> On Wednesday, December 11, 2024 at 03:57:31 PM EST, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> On 12/11/24 11:12, Bharani SV-forum wrote:
>  > Team
>  > As suggested from old server, post shutdown of DB, I did OS level dump
>  > of PG_DATA folder and had restored in the new server.
> 
> If you follow the process shown here:
> 
> https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg%40mail.gmail.com
<https://www.postgresql.org/message-id/CAKAnmmKZdhnhdNRd3OgDyEco9OPkT%3DqA_TeWMFMRvUM9pXauKg%40mail.gmail.com>
> 
> You would not have to do the below.
> 
>  >
>  > Any idea on how to install the older binary postgres 13.18 ( OS=Amazon
>  > Linux 2023.6.20241121) under a dedicated folder suffixed as the
>  > following e.g.) /usr/pgsql1318
>  >
>  > System Admin had already installed newer version pgsql 15.08 binaries in
>  > the  new server (OS= Amazon Linux 2023.6.20241121) in the folder 
> "/usr/bin/"
>  >
>  > We were quoted , OS = Amazon Linux 2023.6.20241121 doesnot support
>  > postgres ver 15.10 (Community edition) under its AWS-EC2.
> 
> That does not reflect well on Amazon Linux, that it is missing two
> critical bug releases.
> 
> 
>  >
>  > Regards
>  >
>  >
>  >
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/16/24 14:30, Bharani SV-forum wrote:
> *a) *
> *user = *
> postgres
> 
> b)
> *pg_dump version = *
> /usr/bin/pg_dump -V
> 
> pg_dump (PostgreSQL) 13.16
> 
> c)
> 
> *DB version*
> 
> select version () ;
>                                                   version
> ----------------------------------------------------------------------------------------------------------
>   PostgreSQL 13.16 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 
> 20150623 (Red Hat 4.8.5-44), 64-bit
> 
> *use this script for backup*
> 
> pg_dump -Fp -p 5432 -U "$USERNAME" "$DATABASE"
> 
> using username = postgres
> 
> for one of the DB (ver 13.16), it worked fine by doing oldvm = pg_dump 
> from ver 13.16 and
> later restoring in new VM with new OS and new db binary 15.09, post 
> creating dummy db (appln related) and restoring the pg_dump from oldvm .
> 

That's nice, but the issue is the case that did not work.

What process where you running that caused the error?


-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/19/24 15:36, Bharani SV-forum wrote:
> 
> cannot drop a tablespace which never exists in pg_tablespace
> 
> I remember i had create previously an tablespace named " mq_data" , but 
> cannot find in pg_tablespace listing.
> 
> if i try to create the same tablespace name, it is giving error as " 
> already in use as a tablespace"
> how to force drop the pointer entry and the tablespace from postgres

From:

https://www.postgresql.org/docs/current/manage-ag-tablespaces.html

"The directory $PGDATA/pg_tblspc contains symbolic links that point to 
each of the non-built-in tablespaces defined in the cluster."

Is there a symlink at the above location?

Does the directory in the image have files?


> 
> Inline image
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/20/24 08:09, Bharani SV-forum wrote:
> Adrian
> Inline image
> 
> initially i had created tblspace outside pg_data env variable

Did you run CREATE TABLESPACE as shown below?:

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

Did you ever use the tablespace?

> e.g PG_DATA env variable is defined to /XXX/YYYY/ABC/15/data
> 
> the tablespace was created under  /XXX/YYYY/ABC/15/tblspace/<<tbl_spcname>>/
> assume tablespace name is abc_data
> 
> *cd /XXX/YYYY/ABC/15/tblspace/abc_data/*
> ls -atl
> drwxr-x---. 2 postgres postgres  6 Dec 19 22:08 PG_15_202209061
> 
> ls -altR
> drwxr-x---. 2 postgres postgres  6 Dec 19 22:08 PG_15_202209061
> 
> i reconfirmed
> SELECT * FROM pg_tablespace ;
>   oid  |  spcname   | spcowner | spcacl | spcoptions
> ------+------------+----------+--------+------------
>   1663 | pg_default |       10 |        |
>   1664 | pg_global  |       10 |        |
> 
> not having any entry about tablespace abc_data
> 
> Can you guide
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/20/24 11:25, Y_Bharani_mbsv wrote:
>   Team
> I have the need to have postgresql db running in multiuser mode and do 
> my needed tasks for few mins.

What are the tasks and why do you think they can't be run concurrently 
with other users?

> 
> How to restrict all the application layer , not to get connected with 
> the postgres db ,
> during my specific time window
> I am aware of their application layer - username
> 
> Changing password is the last option
> 
> Any tips
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

I am in the process of upgrading EC2-PGS ver 13.X to 15.X 

I am aware  since ver 14.X, we have restriction in the usage of schema=public and the DBA need to grant exclusive priv for the tagged db user's.

Any suggestions or best practise

On 12/23/24 11:26 AM, Bharani SV-forum wrote:
> Team
> I am in the process of upgrading EC2-PGS ver 13.X to 15.X
> I am aware  since ver 14.X, we have restriction in the usage of 
> schema=public and the DBA need to grant exclusive priv for the tagged db 
> user's.

Are you referring to this?:

https://www.postgresql.org/docs/15/release-15.html

"Remove PUBLIC creation permission on the public schema (Noah Misch) §

The new default is one of the secure schema usage patterns that Section 
5.9.6 has recommended since the security release for CVE-2018-1058. The 
change applies to new database clusters and to newly-created databases 
in existing clusters. Upgrading a cluster or restoring a database dump 
will preserve public's existing permissions.

For existing databases, especially those having multiple users, consider 
revoking CREATE permission on the public schema to adopt this new 
default. For new databases having no need to defend against insider 
threats, granting CREATE permission will yield the behavior of prior 
releases.
"


> 
> Assume i want to enforce it,
> Can i retag all the object tables/indexex/packages/procedures/functions 
> etc tagged under schema =public to a newly created schema e.g = 
> *schemaname = allowallusr *and grant respective priv's.
> 
> Whether it will resolve the issue, as application time need time to 
> validated all the use case for testing the objects which is present 
> under schema=public and ported to new schema= allowallusr .
> 
> Any suggestions or best practise

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 12/23/24 12:17 PM, Bharani SV-forum wrote:
> Adrian
> TQ. Exactly , you have provided the needed information
> 
> For existing databases, especially those having multiple users,
> - I will consider revoking CREATE permission on the public schema to 
> adopt this new default.

You may want to do some testing before you do that. It may very well be 
that your existing code depends on being able to CREATE objects in the 
public schema using the public role.

> 
> 1) Do i need to revoke "SELECT" access on any tables/indexes etc in 
> schema = public ?
> 2) Do i need to revoke "Execute" access on any procedures/functions  in 
> schema = public ?

Again this is going to need to be tested. I'm betting though that your 
present code depends on these privileges existing.

Just remember the change was for:

"Remove PUBLIC creation permission on the public schema"

where PUBLIC is a built in role. I would suggest reading:

https://www.postgresql.org/docs/current/ddl-priv.html

for more information on what that means.

> 
> 
> I agree with your suggestion - - For new databases having no need to 
> defend against insider threats, granting CREATE permission will yield 
> the behavior of prior releases.

It is not my suggestion, what I quoted comes from the documentation.

> 
> Can you pl seed more information with qsn#1 and #2
> 
> On Monday, December 23, 2024 at 03:06:56 PM EST, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> 
> 
> On 12/23/24 11:26 AM, Bharani SV-forum wrote:
>  > Team
>  > I am in the process of upgrading EC2-PGS ver 13.X to 15.X
>  > I am aware  since ver 14.X, we have restriction in the usage of
>  > schema=public and the DBA need to grant exclusive priv for the tagged db
>  > user's.
> 
> Are you referring to this?:
> 
> https://www.postgresql.org/docs/15/release-15.html 
> <https://www.postgresql.org/docs/15/release-15.html>
> 
> "Remove PUBLIC creation permission on the public schema (Noah Misch) §
> 
> The new default is one of the secure schema usage patterns that Section
> 5.9.6 has recommended since the security release for CVE-2018-1058. The
> change applies to new database clusters and to newly-created databases
> in existing clusters. Upgrading a cluster or restoring a database dump
> will preserve public's existing permissions.
> 
> For existing databases, especially those having multiple users, consider
> revoking CREATE permission on the public schema to adopt this new
> default. For new databases having no need to defend against insider
> threats, granting CREATE permission will yield the behavior of prior
> releases.
> 
> "
> 
> 
>  >
>  > Assume i want to enforce it,
>  > Can i retag all the object tables/indexex/packages/procedures/functions
>  > etc tagged under schema =public to a newly created schema e.g =
>  > *schemaname = allowallusr *and grant respective priv's.
>  >
>  > Whether it will resolve the issue, as application time need time to
>  > validated all the use case for testing the objects which is present
>  > under schema=public and ported to new schema= allowallusr .
>  >
>  > Any suggestions or best practise
> 
> 
> -- 
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 1/28/25 08:23, Bharani SV-forum wrote:
> Team
> Need your help.
> We are trying to use existing VM with underlying OS = Amazon Linux 2 
> (AL2)  along with Pgsql ver 13.X community edn.
> Trying to upgrade from 13.X to 15.X and had hit the bottleneck for the 
> mandate to have python ver 3.X binaries.
> We have limitation with the existing VM with AWS and currently AL2 uses 
> the |yum| package manager that has a hard dependency on Python 2.7 and 
> the pgsql ver 15. needed Ver 3.x python binaries and the package 
> community edition (pgsql ver 15.x) "postgresql15-contrib.." is not 
> getting installed.
> 
> We have limitation , where the application being used is having python 
> ver 2.x binaries and we cannot install python 3.x binaries , as  we have 
> the underlying OS with AL2 which is having "a hard dependency on Python 2.7"
> 
> In lieu of using pgsql ver 15.X. We are OK to upgrade to the next 
> version which is 14.X  from existing ver 13.X.
> 
> Can anyone re-confirm if the Community edition (pgsql ver14.x)  - 
> "postgresql14-contrib .." needed python ver 2.X binaries or Ver 3.X 
> binaries.

 From here:

https://yum.postgresql.org/14/redhat/rhel-7-x86_64/repoview/postgresql14-contrib.html

postgresql14-contrib-14.15-1PGDG.rhel7.x86_64

hstore_plpython3.so
jsonb_plpython3.so
ltree_plpython3.so

So I'm going to say yes Python 3 is needed.

FYI I don't see those files in postgresql13-contrib.

If you want to move forward you need to either install Python 3 in your 
current distro or use a different distro.

> 
> I cross checked and found one of the url " Install Postgres v14 + 
> -contrib on AWS Linux 2 | the gabriellephant 
> <https://gorthx.wordpress.com/2022/02/08/install-postgres-v14-contrib-on-aws-linux-2/>" is quoting pgsql ver 14.x
neededpython ver 3.x binary
 
> 
> On Friday, January 24, 2025 at 02:14:56 PM EST, Adrian Klaver 
> <adrian.klaver@aklaver.com> wrote:
> 
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 1/28/25 12:13, Bharani SV-forum wrote:
> TQ Adrian
> another Question on the measuring egress (out bound traffic) /ingress 
> (inbound traffic) w.r.to " pg_dumpall " during usage of

Since you are using AWS EC2(?) instances wouldn't the AWS dashboard show 
you this?

> 
> pg_dumpall -h  <old vm>  -p 5432 | psql -p 5462
> 
> taking data from old_vm and copying to new_vm, as i need to use across 
> the network for taking data and i cannot use "pg_upgrade" tool as AWS - 
> AL3 doesnot support postgresql 13 - community edition.

The PGDG repo does:

https://www.postgresql.org/download/linux/redhat/

Have you tried using it?

Also from what I gather there is no Amazon Linux 3.

There is Amazon Linux 2023, is that what you are referring to?


> My existing DB size is *around 60 GB* (all the DB's) using postgresql 
> Ver 13.
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 2/16/25 05:13, Y_Bharani_mbsv wrote:
> Team
> Good Morning.
> As part of DB upgrade from EC2 - PGS - community Edn Ver 13.X to 14.X
> I followed steps of "pg_upgrade" and had executed the last step (post 
> successful db migration)
> 
> vacuumdb --analyze-in-stages
> 
> and later noticed an caveat
> url = https://www.postgresql.org/docs/current/app-vacuumdb.html 
> <https://www.postgresql.org/docs/current/app-vacuumdb.html>
> 
> 
> |--analyze-in-stages|
> 
>     Only calculate statistics for use by the optimizer (no vacuum), like
>     |--analyze-only|. Run three stages of analyze; the first stage uses
>     the lowest possible statistics target (see default_statistics_target
>     <https://www.postgresql.org/docs/current/runtime-config-query.html#GUC-DEFAULT-STATISTICS-TARGET>) to produce
usablestatistics faster, and subsequent stages build the full statistics.
 
> 
>     This option is only useful to analyze a database that currently has
>     no statistics or has wholly incorrect ones, such as if it is newly
>     populated from a restored dump or by |pg_upgrade|. *Be aware that
>     running with this option in a database with existing statistics may
>     cause the query optimizer choices to become transiently worse due to
>     the low statistics targets of the early stages.*

Did you skip over reading this part?:

"This option is only useful to analyze a database that currently has no
statistics or has wholly incorrect ones, such as if it is newly 
populated from a restored dump or by pg_upgrade."

> 
> 
> How to overcome the issue to avoid "transiently worse"
> 
> 
> 
>    Later, I too did
> a) vacuum(full,verbose,skip_locked) ... each table wise
> b) analyze (verbose,skip_locked) .. each table wise
> Any guidance
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 2/16/25 08:27, Y_Bharani_mbsv wrote:
> Adrian
> TQ for the instant reply.
> post DB migration to Ver 14.X (successfully) and Post executing the 
> "vacuumdb --analyze-in-stages", i noticed "read me option" and the 
> caveat on it.

Did you do:

vacuumdb --analyze-in-stages

or

vacuumdb --all --analyze-in-stages

?


> 
> Later, I too did
> a) vacuum(full,verbose,skip_locked) ... each table wise b) analyze 
> (verbose,skip_locked) .. each table wise
> against all the DB's

VACUUM FULL has not purpose at this point as FULL recycles unneeded 
tuples from DELETEs and UPDATEs and at this stage there are none of 
those. Also going table by table is not necessary when you can 
vacuuum/analyze an entire database, which is what you want, with one 
command.

> 
> Any guidance on how to overcome the issue.

There is no issue to overcome.

Per:

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

17. Statistics

"Because optimizer statistics are not transferred by pg_upgrade, you 
will be instructed to run a command to regenerate that information at 
the end of the upgrade. You might need to set connection parameters to 
match your new cluster."

Running vacuumdb --all --analyze-in-stages will create the statistics 
you need it just does it in steps(stages) vs doing vacuumdb --all 
--analyze-only which does it in a single pass. Unless you are planning 
to run some large complicated queries immediately upon completion of the 
upgrade you will not notice the difference.

> Any suggestion ?
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 2/16/25 09:43, Bharani SV-forum wrote:
> Adrian
> Post pg_upgrade command (success ) from DB ver 13.X to 14.X,
> I had used following command
> 
> vacuumdb --all --analyze-in-stages

You are done then, move on.

> 
> Need your best suggestion to avoid any unknown headache

Keep on moving forward. 'unknown headache' is not something I can help with.


-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 4/2/25 08:18, Bharani SV-forum wrote:
> Hello MVP's
> Good Morning
> Any industry best practise to overcome this specific malware "pg_mem".
> 
> url = 
> https://www.aquasec.com/blog/pg_mem-a-malware-hidden-in-the-postgres-processes/
<https://www.aquasec.com/blog/pg_mem-a-malware-hidden-in-the-postgres-processes/>

 From above:

"The first stage is a simple brute force attack. We observe several 
login attempts to the PostgreSQL database being refused until the brute 
force attack successfully guesses the honeypot’s username and password 
(which were intentionally set to be easy to guess)."

After the threat actor successfully guess the user and password, the 
attack sequence commenced. The following set of SQL commands, were 
executed: ...
"

The first command being creating a role with SUPERUSER privileges which 
depends the hacked role being a SUPERUSER itself.


So the solution is basic practices:

1) Don't expose the database anymore then necessary. It other words keep 
access to the instance as restricted as possible, e.g. behind firewall.

2) Don't use easy passwords or use one or more of the auth methods shown 
here:

https://www.postgresql.org/docs/current/client-authentication.html

3) Try to avoid using SUPERUSER roles as login roles.

Keeping up to date is good practice, but in and of itself it will not 
prevent the attack shown.

> 
> We are up to date with the respective postgres server major version 13 
> and minor patch as .20
> i.e 13.20
> Also working on the steps for db migration from ver 13.X to ver 14.X
> We are also update with respective AWS based EC2 server based OS patches

-- 
Adrian Klaver
adrian.klaver@aklaver.com