Cluster forcefully removal without user input

[Zaid Shabbir]

Hello,

I have installed PostgreSQL 15 and PostgreSQL 14 side by side and want to
upgrade from 14 to 15. For upgrading purposes, I am using {postgresql-15-setup
check_upgrade}. However, in my case, the installed 14 version is not
compatible with the latest 15.7.

After the installation and cluster initialization of PostgreSQL 14 and 15,
when I run the following command {postgresql-15-setup check_upgrade}, it
returns the following message:
"Performing upgrade check: Upgrade failed. Removing the new cluster. Please
re-initdb the new cluster. failed "


After the failure the postgresql15 cluster removed forcefully due to the
following code written in postgresql-15-setup script file

{
if [ $script_result -eq 0 ]; then
echo $"OK"
else
# Clean up after failure
echo "Upgrade failed. Removing the new cluster. Please re-initdb
the new cluster."

*rm -rf "$PGDATA"*echo $"failed"
fi
}

My concern here is whether forcefully deleting the user cluster without
obtaining permission from the user is the right approach.



Regards,
Zaid Shabbir
AGEDB

Re: broken devel package for rocky linux

[Zaid Shabbir]

Got it, Thank you.

On Tue, Sep 3, 2024 at 3:55 PM Devrim Gündüz  wrote:

> Hi,
>
> On Tue, 2024-09-03 at 15:48 +0500, Zaid Shabbir wrote:
> > This information is missing on the PostgreSQL packages installation
> > configuration page. I think it's helpful if we provide the information
> > on
> > the relevant page.
> > https://www.postgresql.org/download/linux/redhat/
>
> That page is not intended for -devel subpackage users. Please read
> details instructions here:
>
> https://yum.postgresql.org/howto/
>
> Regards,
> --
> Devrim Gündüz
> Open Source Solution Architect, PostgreSQL Major Contributor
> Twitter: @DevrimGunduz , @DevrimGunduzTR
>

Re: [ pg_ctl ] Review Request for Adding Pre-check User Script Feature

[Zaid Shabbir]

Hello,

Can you briefly explain what’s the issues you are going through the patch?


On Tue, 16 Jul 2024 at 11:40 AM, 김명준  wrote:

> Hello,
>
> I have been considering adding a user script that performs pre-checks
> before executing the start, stop, and restart operations in pg_ctl. I
> believe it is necessary for pg_ctl to support an extension that can prevent
> various issues that might occur when using start and stop. To this end, I
> have sought a way for users to define and use their own logic. The existing
> behavior remains unchanged, and the feature can be used optionally when
> needed.
>
> The verification of the code was carried out using the methods described
> below, and I would like to request additional opinions or feedback. Tests
> were conducted using make check and through direct testing under various
> scenarios. As this is my first contribution, there might be aspects I
> missed or incorrectly designed.
>
> I would appreciate it if you could review this.
>
> Thank you.
>
>
> Myoungjun Kim / South Korea
>

Re: Windows default locale vs initdb

[Zaid Shabbir]

Hello Thomas,

Can you please list down some of the use cases for the patch ? Other than
Turkish, does this patch have an impact on other locales too ?


Regards,
Zaid


On Mon, Jul 22, 2024 at 7:52 AM Thomas Munro  wrote:

> Ertan Küçükoglu offered to try to review and test this, so here's a rebase.
>
> Some notes:
>
> * it turned out that the Turkish i/I test problem I mentioned earlier
> in this thread[1] was just always broken on Windows, we just didn't
> ever test with UTF-8 before Meson took over; it's skipped now, see
> commit cff4e5a3[2]
>
> * it seems that you can't actually put encodings like .1252 on the end
> (.UTF-8 must be a special case); I don't know if we should look into a
> better UTF-8 mode for modern Windows, but that'd be a separate project
>
> * this patch only benefits people who run initdb.exe without
> explicitly specifying a locale; probably a good number of real systems
> in the wild actually use EDB's graphical installer which initialises a
> cluster and has its own way of choosing the locale, as discussed in
> Ertan's thread[3]
>
> [1]
> https://www.postgresql.org/message-id/flat/CA%2BhUKGJZskvCh%3DQm75UkHrY6c1QZUuC92Po9rponj1BbLmcMEA%40mail.gmail.com#3a00c08214a4285d2f3c4297b0ac2be2
> [2] https://github.com/postgres/postgres/commit/cff4e5a3
> [3]
> https://www.postgresql.org/message-id/flat/CAH2i4ydECHZPxEBB7gtRG3vROv7a0d3tqAFXzcJWQ9hRsc1znQ%40mail.gmail.com
>

OLEDB provider for PostgreSQL

[Zaid Shabbir]

Hello,

I am looking for an OLEDB provider for PostgreSQL 16 or later. I found one
link, but it seems that it does not support PostgreSQL 16+ and,
additionally, it is not free.

PostgreSQL: PostgreSQL Native OLEDB Provider (PGNP) 1.3.0 32/64-bit
released!
<https://www.postgresql.org/about/news/postgresql-native-oledb-provider-pgnp-130-3264-bit-released-1153/>

Any other suitable OLEDB provider ?

Regards,
Zaid Shabbir

All supported PostgreSQL 17 extensions list

[Zaid Shabbir]

Hello Hackers,

I’m looking for a complete list of PostgreSQL 17 extensions — both
open-source and proprietary. I found a link
<https://www.postgresql.org/download/products/6-postgresql-extensions/>,
but it doesn’t seem to include all available extensions.

Is there an official or community-maintained source where I can find a
comprehensive list of supported extensions?


Thanks & Regards,

Zaid Shabbir