Re: Editor access request

Поиск
Список
Период
Сортировка
Искать

Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
On 7/13/26 11:17, Super wrote:
> I would like editor access to the wiki. My username is superlede.

I expedited your cooling off period. Please login to the wiki once and 
then reply-all to this email saying that you have done so. At that point 
we can grant editor access.

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Super <thinklong.super@gmail.com>
Дата:
Hi Joe,

Done — I've logged in to the wiki once with my community account (username: superlede).

Thanks for expediting this.

Super

On Tue, Jul 14, 2026 at 1:08 AM Joe Conway <mail@joeconway.com> wrote:
On 7/13/26 11:17, Super wrote:
> I would like editor access to the wiki. My username is superlede.

I expedited your cooling off period. Please login to the wiki once and
then reply-all to this email saying that you have done so. At that point
we can grant editor access.

--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
On 7/13/26 13:22, Super wrote:
> Done — I've logged in to the wiki once with my community account 
> (username: superlede).


For some reason I am not seeing that you have logged in. Maybe try again 
¯\_(ツ)_/¯

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
Please keep all replies on the public lists

No change, still no evidence of a log in.

I also note that this reply comes from a different email address which 
also has another community account, which is also in cooling off period.

I need confirmation from the original email address that these two are 
in fact owned by the same person.


On 7/13/26 14:07, Bilal Abdulkadir Muhammed wrote:
>   Subject: Re: Wiki Account Login
> 
> Hi,
> 
> Thank you for letting me know. I have just logged in again using my 
> community account (superlede). Could you please check if the login is 
> now visible on your end?
> 
> If it still doesn't appear, I'd be happy to try any additional steps you 
> recommend.
> 
> Thank you for your assistance.
> 
> Best regards,
> Bilal Abdulkadir Muhammed
> 
> On Mon, 13 Jul 2026, 8:57 pm Joe Conway,  > wrote:
> 
>     On 7/13/26 13:22, Super wrote:
>      > Done — I've logged in to the wiki once with my community account
>      > (username: superlede).
> 
> 
>     For some reason I am not seeing that you have logged in. Maybe try
>     again
>     ¯\_(ツ)_/¯
> 
>     -- 
>     Joe Conway
>     PostgreSQL Contributors Team
>     Amazon Web Services: https://aws.amazon.com 
> 
> 


-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Super <thinklong.super@gmail.com>
Дата:
I have logged in again, please check it (username: superlede)

Thanks.

On Tue, Jul 14, 2026 at 1:57 AM Joe Conway <mail@joeconway.com> wrote:
On 7/13/26 13:22, Super wrote:
> Done — I've logged in to the wiki once with my community account
> (username: superlede).


For some reason I am not seeing that you have logged in. Maybe try again
¯\_(ツ)_/¯

--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
On 7/13/26 14:23, Super wrote:
> I have logged in again, please check it (username: superlede)

I still cannot see a valid wiki account. Did you log into the wiki itself?

By the way, please confirm or deny that this email is also you:

   Bilal Abdulkadir Muhammed 

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
On 7/14/26 11:30, Super wrote:
> Hi Joe, I’ve now logged in directly through the “Log in” link on the 
> PostgreSQL Wiki itself, and the wiki shows me as logged in with the 
> username “superlede”.

Great -- I have provided editor access to you now

> The email address bilalabdulkadir286@gmail.com
>  is not mine and is not
> associated with me. Could you please check again?

Thanks for confirming. This email claimed to be you and claimed to have 
logged in as username “superlede”. Not sure what they hoped to gain but 
worth taking note.

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Bilal Abdulkadir Muhammed <bilalabdulkadir286@gmail.com>
Дата:
Вложения:
Subject: Re: PostgreSQL Wiki Account Verification
Hi Joe,

Thank you for looking into this.

I have now logged in directly through the PostgreSQL Wiki's “Log in” link, and the wiki shows me as authenticated with the username “superlede.”

I have attached a screenshot for verification. As you can see, the account is logged in and associated with the PostgreSQL services. The email address bilalabdulkadir286@gmail.com shown in the screenshot belongs to me and is the address currently linked to my PostgreSQL account and mailing-list subscriptions.

Could you please review the account details again and confirm whether the username superlede is correctly associated with my email address and eligible for the requested access?

Thank you for your assistance.
Best regards,
Super (superlede)


From: Joe Conway <mail@joeconway.com>
Sent: Tuesday, 14 July 2026 19:34:14
To: Super <thinklong.super@gmail.com>
Cc: pgsql-www@postgresql.org <pgsql-www@postgresql.org>
Subject: Re: Editor access request
 
On 7/14/26 11:30, Super wrote:
> Hi Joe, I’ve now logged in directly through the “Log in” link on the
> PostgreSQL Wiki itself, and the wiki shows me as logged in with the
> username “superlede”.

Great -- I have provided editor access to you now

> The email address bilalabdulkadir286@gmail.com
> <mailto:bilalabdulkadir286@gmail.com> is not mine and is not
> associated with me. Could you please check again?

Thanks for confirming. This email claimed to be you and claimed to have
logged in as username “superlede”. Not sure what they hoped to gain but
worth taking note.

--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Joe Conway <mail@joeconway.com>
Дата:
On 7/14/26 12:41, Bilal Abdulkadir Muhammed wrote:
> Subject: Re: PostgreSQL Wiki Account Verification
> Hi Joe,
> 
> Thank you for looking into this.
> 
> I have now logged in directly through the PostgreSQL Wiki's “Log in” 
> link, and the wiki shows me as authenticated with the username “superlede.”
> 
> I have attached a screenshot for verification. As you can see, the 
> account is logged in and associated with the PostgreSQL services. The 
> email address *bilalabdulkadir286@gmail.com* shown in the screenshot 
> belongs to me and is the address currently linked to my PostgreSQL 
> account and mailing-list subscriptions.


This is too weird -- I am not touching that attachment with a 10 foot pole.

-- 
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com


Re: Editor access request

От:
Bilal Abdulkadir Muhammed <bilalabdulkadir286@gmail.com>
Дата:
Subject: Re: PostgreSQL Wiki Account Verification

Hi Joe,
To confirm without attachments:
I am logged in through the PostgreSQL Wiki’s “Log in” link.

My authenticated username is superlede.The account is linked to bilalabdulkadir286@gmail.com, which is also the address subscribed to PostgreSQL mailing lists.Please let me know if further steps are required to ensure my mailing list access remains active and properly associated with this account.Thank you for your support.

Best regards,
Bilal Abdulkadir Muhammed

On Tue, 14 Jul 2026, 7:49 pm Joe Conway, <mail@joeconway.com> wrote:
On 7/14/26 12:41, Bilal Abdulkadir Muhammed wrote:
> Subject: Re: PostgreSQL Wiki Account Verification
> Hi Joe,
>
> Thank you for looking into this.
>
> I have now logged in directly through the PostgreSQL Wiki's “Log in”
> link, and the wiki shows me as authenticated with the username “superlede.”
>
> I have attached a screenshot for verification. As you can see, the
> account is logged in and associated with the PostgreSQL services. The
> email address *bilalabdulkadir286@gmail.com* shown in the screenshot
> belongs to me and is the address currently linked to my PostgreSQL
> account and mailing-list subscriptions.


This is too weird -- I am not touching that attachment with a 10 foot pole.

--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com

Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy

От:
Ron Johnson <ronljohnsonjr@gmail.com>
Дата:
On Wed, Sep 9, 2026 at 4:47 AM Cipriani, Ivan <ivan.cipriani@gehealthcare.com> wrote:

Dear Postgres Community,

We started to use PostgreSQL database for our project, and we are happy so far 😊 But we are facing one dilemma and would like to have your recommendation about it. 

To keep things up to date, we are going to regularly upgrade the version of PostgreSQL we are using. Also, in our product, we have functionality for backing up and restoring database. Sometimes customers do restore from older versions, and we will need to support restoring database from multiple older versions. 


How were those backups taken?
 

We tried to use the following approaches: 

  • pg_basebackup + pg_upgrade 

This works fast enough and gives us a physical cluster backup. However, pg_upgrade requires not only new binaries to work, but also the older binaries matching the version database backup was created with. It brings us a bit of confusion as it’s problematic to ship all the previous versions of PostgreSQL binaries to support database restore. 


Postgresql binaries from https://ftp.postgresql.org/ are multi-version, so you can leave those old binaries on disk alongside the "current" binaries.  That won't work, though, when you upgrade the distro version...
 

  • pg_dump + pg_restore 

This is version-independent and works well across PostgreSQL major versions. However, restore time is much slower because PostgreSQL must reload all data and rebuild indexes, constraints, and metadata. With large databases it can become an issue.


How often do you all do these restores?
 

Also, requires additional steps to protect data. 

So, we would like to ask these questions: 

1. Is there some other intended way of doing backup/restore that should be used with PostgreSQL? Have we probably missed some proper way of doing it? 


pg_dump + pg_restore are the OS-neutral, distro version-neutral, PG-neutral way to do backups and restores.
 
For example, it's your only choice to restore a PG 10 database which lived on a RHEL7 server into a PG 18 instance on RHEL9 or Debian or SUSE.

2. If we will use pg_upgrade, does it require all the binaries or probably only just certain DLLs/tools from bin folder that we can keep with database backup? 


PG is not Oracle... 😀  For example, the PG 17 directory tree is IIRC 20MB.  Thus, you can keep all the versions on disk.
 

3. Also, is it intended that pg_upgrade will work with any minor versions across the major version provided? For example, if we 

have old database created with version 18.1, will it work with binaries version 18.9, or can it depend on actual version changes?  


The database "on-disk structure" does not change across minor versions.  (The "on-disk structure" doesn't really change between major versions. It's the catalog tables which change.)

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

Re: Seeking Recommendations for PostgreSQL Backup, Restore, and Upgrade Strategy

От:
Muhammed Ali Demirci <dmrc.muhammedali@gmail.com>
Дата:
 Hello, there seems to have been a mistake; I’ve just realized that I was included in the CC list for numerous emails. I am removing myself from the mailing list. I wish you all success with the project you are working on.

Ron Johnson <ronljohnsonjr@gmail.com>, 9 Eyl 2026 Çar, 14:13 tarihinde şunu yazdı:
On Wed, Sep 9, 2026 at 4:47 AM Cipriani, Ivan <ivan.cipriani@gehealthcare.com> wrote:

Dear Postgres Community,

We started to use PostgreSQL database for our project, and we are happy so far 😊 But we are facing one dilemma and would like to have your recommendation about it. 

To keep things up to date, we are going to regularly upgrade the version of PostgreSQL we are using. Also, in our product, we have functionality for backing up and restoring database. Sometimes customers do restore from older versions, and we will need to support restoring database from multiple older versions. 


How were those backups taken?
 

We tried to use the following approaches: 

  • pg_basebackup + pg_upgrade 

This works fast enough and gives us a physical cluster backup. However, pg_upgrade requires not only new binaries to work, but also the older binaries matching the version database backup was created with. It brings us a bit of confusion as it’s problematic to ship all the previous versions of PostgreSQL binaries to support database restore. 


Postgresql binaries from https://ftp.postgresql.org/ are multi-version, so you can leave those old binaries on disk alongside the "current" binaries.  That won't work, though, when you upgrade the distro version...
 

  • pg_dump + pg_restore 

This is version-independent and works well across PostgreSQL major versions. However, restore time is much slower because PostgreSQL must reload all data and rebuild indexes, constraints, and metadata. With large databases it can become an issue.


How often do you all do these restores?
 

Also, requires additional steps to protect data. 

So, we would like to ask these questions: 

1. Is there some other intended way of doing backup/restore that should be used with PostgreSQL? Have we probably missed some proper way of doing it? 


pg_dump + pg_restore are the OS-neutral, distro version-neutral, PG-neutral way to do backups and restores.
 
For example, it's your only choice to restore a PG 10 database which lived on a RHEL7 server into a PG 18 instance on RHEL9 or Debian or SUSE.

2. If we will use pg_upgrade, does it require all the binaries or probably only just certain DLLs/tools from bin folder that we can keep with database backup? 


PG is not Oracle... 😀  For example, the PG 17 directory tree is IIRC 20MB.  Thus, you can keep all the versions on disk.
 

3. Also, is it intended that pg_upgrade will work with any minor versions across the major version provided? For example, if we 

have old database created with version 18.1, will it work with binaries version 18.9, or can it depend on actual version changes?  


The database "on-disk structure" does not change across minor versions.  (The "on-disk structure" doesn't really change between major versions. It's the catalog tables which change.)

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