Re: Upgrading PG11 to PG17 without dump/restore

On 2025-05-01 23:06, Durumdara wrote: The PG_Upgrade is not possible because of lesser space and too old debian. As a data point, pg_upgrade has an option to do an in-place upgrade which reuses the vast majority of the data files as they are on disk, rather than making a copy. It's useful

Re: Upgrading PG11 to PG17 without dump/restore

On 5/1/25 06:06, Durumdara wrote: Hello! There is a heavily used server, with older debian, and PG11. The data is more than 1,2 TB. The PG_Upgrade is not possible because of lesser space and too old debian. 1) Specify what the old and new versions of Debian are. 2) I don't understand what the

Re: Upgrading PG11 to PG17 without dump/restore

On Thu, May 1, 2025 at 9:06 AM Durumdara wrote: > Hello! > > There is a heavily used server, with older debian, and PG11. > The data is more than 1,2 TB. > The PG_Upgrade is not possible because of lesser space and too old debian. > > As we see now we have only one way to move this server. > 1.)

Re: Upgrading from v12.7 to v15.7

Hi, Cstore -https://github.com/citusdata/cstore_fdw Oracle_fdw - https://github.com/laurenz/oracle_fdw/releases/tag/ORACLE_FDW_2_6_0 On Mon, Jul 8, 2024, 19:52 Yongye Serkfem wrote: > Hello Engineers, > After upgrading from v12.7 to v15.7, I ran the following command and got > this error mess

Re: Upgrading

You can see this document. https://www.postgresql.org/docs/current/pgupgrade.html Yours, Wen Yi ---Original--- From: "Amn Ojee Uw"

Re: Upgrading

On 7/30/23 19:22, Amn Ojee Uw wrote: Thank you Ron and Peter for taking the time to respond to my call for help. In summery, I'd like to use PostgreSQL-15. However, since my Debian 12 already has already PostgreSQL-15 installed, did I inadvertently overwrote PostgreSQL-15 when I installed Pos

Re: Upgrading

Thank you Ron and Peter for taking the time to respond to my call for help. In summery, I'd like to use PostgreSQL-15. However, since my Debian 12 already has already PostgreSQL-15 installed, did I inadvertently overwrote PostgreSQL-15 when I installed PostgreSQL-12? If so, how do I remove Pos

Re: Upgrading

On 2023-07-30 07:53:54 -0400, Amn Ojee Uw wrote: > On my Debian 12, I installed PostgreSQL-12, Where did you install that from? AFAICS, Debian 12 comes with PostgreSQL 15. > I'd like to upgrade to the latest release of PostgreSQL. So, my > question is, what is the best way to upgrade to the next

Re: Upgrading

On 7/30/23 06:53, Amn Ojee Uw wrote: Just a quick question. On my Debian 12, I installed PostgreSQL-12, I'd like to upgrade to the latest release of PostgreSQL. So, my question is, what is the best way to upgrade to the next release of PostgreSQL? To the latest release of v12 (which is 12.15

Re: Upgrading to v12

On 11/28/22 17:02, Tom Lane wrote: Brad White writes: I tried to run initdb after re-installing pg 12 using postgresql-12.10-2-windows-x64.exe. But the runas I'm using to execute it as pguser seems to be swallowing all the output, so I can't see any errors. I was able to run pg_checksums and ge

Re: Upgrading to v12

Brad White writes: > I tried to run initdb after re-installing pg 12 > using postgresql-12.10-2-windows-x64.exe. > But the runas I'm using to execute it as pguser seems to be swallowing all > the output, so I can't see any errors. > I was able to run pg_checksums and get those enabled. > Is there

Re: Upgrading to v12

Tom, I tried to run initdb after re-installing pg 12 using postgresql-12.10-2-windows-x64.exe. But the runas I'm using to execute it as pguser seems to be swallowing all the output, so I can't see any errors. I was able to run pg_checksums and get those enabled. Is there anything else I want from i

Re: Upgrading to v12

On 11/22/22 12:53, Brad White wrote: On 11/18/2022 6:34 PM, Adrian Klaver wrote: On 11/18/22 16:05, Brad White wrote: --> The Microsoft Access database engine stopped the process because you and another user are attempting to change the same data at the same time. Code in question:       

Re: Upgrading to v12

On 11/18/2022 6:34 PM, Adrian Klaver wrote: On 11/18/22 16:05, Brad White wrote: --> The Microsoft Access database engine stopped the process because you and another user are attempting to change the same data at the same time. Code in question:       rst!Update  <-- success       rst!Qty

Re: Upgrading to v12

On 11/18/22 16:05, Brad White wrote: tl;dr  How do I turn up the logging so I can see what is failing? In our quest to get replication working, we are upgrading from v9.4 to v12.10. Access365 via ODBC Driver = "PostgreSQL Unicode" v13.02, Date 9/22/2021 In testing the app against v12, I find

Re: Upgrading to v12

tl;dr How do I turn up the logging so I can see what is failing? In our quest to get replication working, we are upgrading from v9.4 to v12.10. Access365 via ODBC Driver = "PostgreSQL Unicode" v13.02, Date 9/22/2021 In testing the app against v12, I find this issue: On updating a record, I set

Re: Upgrading to v12

On 11/12/22 22:07, Tom Lane wrote: Ron writes: On 11/11/22 23:09, Adrian Klaver wrote: 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore of said dump file to version 12. When moving up in version you ne

Re: Upgrading to v12

On 11/12/22 18:18, Brad White wrote: >  How where the restored copies made on the original cluster? I guess I'm not understanding the confusion here. They were restored with the same script but to a different DB name and with the 9.4 executables. In fact, that was why the scr

Re: Upgrading to v12

Ron writes: > On 11/11/22 23:09, Adrian Klaver wrote: >> 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore >> 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore >> of said dump file to version 12. When moving up in version you need to use >> the newer ve

Re: Upgrading to v12

On 11/11/22 23:09, Adrian Klaver wrote: On 11/11/22 20:59, Brad White wrote: On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver > wrote: Yes. The backup is from production. V9.4 is running on 5432 on all servers. That particular restore happens to be on the dev serve

Re: Upgrading to v12

> > > > How where the restored copies made on the original cluster? > I guess I'm not understanding the confusion here. They were restored with > the same script but to a different DB name and with the 9.4 executables. > In fact, that was why the script was originally written, so we could > restor

Re: Upgrading to v12

> If the client lets you, of course. Right? 8: -) That's not a concern here. A) They trust me, and B) They only see the front end. They don't really care what happens with the back end. so long as A) It doesn't break, and B) We get replication working. >

Re: Upgrading to v12

> Step #1: upgrade to 9.4.26. You'll get *five years* of bug fixes. Good idea. I'll try 12 first, and if that doesn't work we'll go with this. >

Re: Upgrading to v12

> When moving up in version you need to use the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4 instance and then the version 12 pg_restore to the 12 instance. Oh my. That's a substantial change that could make a difference. Thanks for catching that. > >

Re: Upgrading to v12

Step #1: upgrade to 9.4.26.  You'll get *five years* of bug fixes. (If the client lets you, of course.  I had servers stuck on 8.4.17 and 9.2.7 that were only upgraded because PCI auditors were going to tell my client's client, and that scared /my/ client.  Now they're on 9.6.24...) On 11/11/

Re: Upgrading to v12

On 11/11/22 20:59, Brad White wrote: On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver > wrote: Yes. The backup is from production. V9.4 is running on 5432 on all servers. That particular restore happens to be on the dev server. 5433 is v12. 1) This does not addre

Re: Upgrading to v12

On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver wrote: > On 11/11/22 18:41, Brad White wrote: > > > From your original post, what did "Not the half dozen restored copies" > > mean? > > Over time, we've restored multiple copies for testing and reproducing > > various issues. > > > > I'm only trying t

Re: Upgrading to v12

On 11/11/22 18:41, Brad White wrote: > From your original post, what did "Not the half dozen restored copies" mean? Over time, we've restored multiple copies for testing and reproducing various issues. I'm only trying to set up replication one one of those copies. > In other words define th

Re: Upgrading to v12

Sorry. Ignore the errors. That was mistakenly copied in from elsewhere.

Re: Upgrading to v12

> From your original post, what did "Not the half dozen restored copies" mean? Over time, we've restored multiple copies for testing and reproducing various issues. I'm only trying to set up replication one one of those copies. > In other words define the restore process. Command to back up the

Re: Upgrading to v12

On 11/11/22 14:06, Brad White wrote: > Can you do a pg_dump of that database? Yes. No visible problems. No errors reported. From your original post, what did "Not the half dozen restored copies" mean? In other words define the restore process. -- Adrian Klaver adrian.kla...@aklaver.com

Re: Upgrading to v12

Brad White writes: >> Can you do a pg_dump of that database? > Yes. No visible problems. No errors reported. Well, that's quite interesting, because pg_dump ought to read all the same catalogs that pg_upgrade is failing to read. So I'm not quite sure what's going on there. Nonetheless, your pat

Re: Upgrading to v12

> Can you do a pg_dump of that database? Yes. No visible problems. No errors reported. On Fri, Nov 11, 2022 at 3:17 PM Adrian Klaver wrote: > On 11/11/22 13:11, Brad White wrote: > > I deleted all the other DBs and left only the primary. > > Still getting the same error message, ending with > >

Re: Upgrading to v12

I'm practicing on our Dev server, so I can blow this away and reload at any time. Are there any utilities to check for corruption on my Prod server in v9.4.1? All my backups are done with pg_dump.exe, so that's where this database came from in the first place. So we know that pg_dump.exe works on

Re: Upgrading to v12

On 11/11/22 13:11, Brad White wrote: I deleted all the other DBs and left only the primary. Still getting the same error message, ending with ERROR:  could not access status of transaction 22316920 DETAIL:  Could not read from file "pg_clog/0015" at offset 73728: No error. Can you do a pg_dump

Re: Upgrading to v12

Brad White writes: > I deleted all the other DBs and left only the primary. > Still getting the same error message, ending with > ERROR: could not access status of transaction 22316920 > DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error. That's a pretty clear indication

Re: Upgrading to v12

I deleted all the other DBs and left only the primary. Still getting the same error message, ending with ERROR: could not access status of transaction 22316920 DETAIL: Could not read from file "pg_clog/0015" at offset 73728: No error.

Re: Upgrading to v12

> What was the complete pg_upgrade command you used? "C:\Program Files\PostgreSQL\12\bin\pg_upgrade" -d "C:\Program Files\PostgreSQL\9.4\data" -D "C:\Program Files\PostgreSQL\12\data" -b "C:\Program Files\PostgreSQL\9.4\bin" -B "C:\Program Files\PostgreSQL\12\bin" -U postgres -p 5432 -P 5435 > >

Re: Upgrading to v12

On 11/11/22 12:43, Brad White wrote: I'm upgrading from v9.4 to v12.10 as a half step to 15. Q1: How do I tell it which database to upgrade? I only need the primary. Not the half dozen restored copies. Or do I need to detach everything I don't want copied? 1) If you are using pg_upgrade then i

Re: Upgrading error

This is the log I got. - pg_upgrade run on Mon Oct 24 07:41:13 2022 - command: "/usr/pgsql-12/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D "/home/dmartuser/pgdata/data"

Re: Upgrading error

Hi, Thanks for the reply! Sorry I missed that line, but now I'm having new error. [root@datamartds tmp]# sudo su postgres bash-4.4$ cd /tmp bash-4.4$ /usr/pgsql-14/bin/pg_upgrade --old-datadir=/home/dmartuser/pgdata/data/ --new-datadir=/home/dmartuser/pgsql/14/data/ --old-bindir=/usr/pgsql-12/bi

Re: Upgrading error

chris navarroza writes: > could not connect to source postmaster started with the command: > "/usr/pgsql-12/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D > "/home/dmartuser/pgdata/data" -o "-p 50432 -b -c > config_file=/var/lib/pgsql/12/data/postgresql.conf -c listen_addresses='' > -c unix_socket_p

Re: Upgrading error

chris navarroza writes: > bash-4.4$ /usr/pgsql-14/bin/pg_upgrade > --old-datadir=/home/dmartuser/pgdata/data/ > --new-datadir=/home/dmartuser/pgdata/data/ --old-bindir=/usr/pgsql-12/bin/ > --new-bindir=/usr/pgsql-14/bin/ --check --verbose > Running in verbose mode > Performing Consistency Checks >

Re: Upgrading from 12.3 to 12.11

-general@lists.postgresql.org Subject: Re: Upgrading from 12.3 to 12.11 On 8/3/22 11:44 AM, zaphod61 wrote:> The server version is 2016. The installer is the one listed on the > postgresql support page.  I think version 12.3 was installed the same > way but that was before I came into con

Re: Upgrading from 12.3 to 12.11

On 8/3/22 11:44, zaphod61 wrote: The server version is 2016. The installer is the one listed on the postgresql support page.  I think version 12.3 was installed the same way but that was before I came into contact with this application Would be helpful to do: select version(); to get some

Re: Upgrading from 12.3 to 12.11

cause a mess. Also how much downtime can you tolerate? Sent from my Verizon, Samsung Galaxy smartphone Original message From: Adrian Klaver Date: 8/3/22 1:57 PM (GMT-05:00) To: zaphod61 , pgsql-general@lists.postgresql.org Subject: Re: Upgrading from 12.3 to 12.11 On 8

Re: Upgrading from 12.3 to 12.11

: Adrian Klaver Date: 8/3/22 1:57 PM (GMT-05:00) To: zaphod61 , pgsql-general@lists.postgresql.org Subject: Re: Upgrading from 12.3 to 12.11 On 8/3/22 10:16 AM, zaphod61 wrote:> > I've inherited a postgresql 12.3 installation. It has 1 database in it.  > I need to upgrade it to the

Re: Upgrading from 12.3 to 12.11

On 8/3/22 10:16 AM, zaphod61 wrote: I've inherited a postgresql 12.3 installation. It has 1 database in it. I need to upgrade it to the newest version, which appears to be 12.11. Can I just download the installer for 12 11 and run that to upgrade the product and still maintain access to the

Re: Upgrading from 12.3 to 12.11

> On Aug 3, 2022, at 10:16, zaphod61 wrote: > > > I've inherited a postgresql 12.3 installation. It has 1 database in it. I > need to upgrade it to the newest version, which appears to be 12.11. Can I > just download the installer for 12 > 11 and run that to upgrade the product and still m

Re: Upgrading from 12.3 to 12.11

On Wednesday, August 3, 2022, zaphod61 wrote: > > I've inherited a postgresql 12.3 installation. It has 1 database in it. I > need to upgrade it to the newest version, which appears to be 12.11. Can I > just download the installer for 12 > 11 and run that to upgrade the product and still maintai

Re: Upgrading from 11 to 13

On 4/3/21 12:47 PM, Koen De Groote wrote: If an upgrade process has a part where old functionality doesn't work anymore, or anything at all breaks, then it's not "you can just upgrade no problems". Major versions are allowed to break compatibility, so there is always a chance for issues. Th

Re: Upgrading from 11 to 13

On Sat, Apr 3, 2021 at 09:47:10PM +0200, Koen De Groote wrote: > If an upgrade process has a part where old functionality doesn't work anymore, > or anything at all breaks, then it's not "you can just upgrade no problems". Well, stopping at every major release between major releases dosen't help

Re: Upgrading from 11 to 13

If an upgrade process has a part where old functionality doesn't work anymore, or anything at all breaks, then it's not "you can just upgrade no problems". On Sat, Apr 3, 2021 at 8:50 PM Adrian Klaver wrote: > On 4/3/21 10:37 AM, Koen De Groote wrote: > > Yes that's it. Probably something to ale

Re: Upgrading from 11 to 13

On 2021-04-01 21:56:17 -0400, Bruce Momjian wrote: > On Thu, Apr 1, 2021 at 09:55:28PM -0400, Bruce Momjian wrote: > > Here it is with descriptions: > > Sorry, please ignore. Too late. Now we all know the code names for previous PostgreSQL releases. hp -- _ | Peter J. Holzer|

Re: Upgrading from 11 to 13

On 4/3/21 10:37 AM, Koen De Groote wrote: Yes that's it. Probably something to alert people to. If they have this set up, they can't "just to straight to 13". Yes you can. You run into the same issue going from 11 --> 12 --> 13, you would just hit it in a different portion of the process.

Re: Upgrading from 11 to 13

Yes that's it. Probably something to alert people to. If they have this set up, they can't "just to straight to 13". On Fri, Apr 2, 2021 at 1:32 AM Alvaro Herrera wrote: > On 2021-Apr-02, Koen De Groote wrote: > > > I seem to recall that going from 11 to 12, a certain configuration file > was >

Re: Upgrading from 11 to 13

On Thu, Apr 1, 2021 at 09:55:28PM -0400, Bruce Momjian wrote: > > Here it is with descriptions: Sorry, please ignore. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusio

Re: Upgrading from 11 to 13

Here it is with descriptions: Hepatitis A Dates on file: 09/01/2005, 01/27/2005 IPV (Polio) Dates on file: 09/01/2005 Influenza Vaccine Quadrivalent 3 Yr And Older Dates on file: 08/25/2020, 10/19/2015 Influenza V

Re: Upgrading from 11 to 13

On Thu, Apr 1, 2021 at 07:26:14PM -0400, Jonathan Katz wrote: > On 4/1/21 6:06 PM, Bruce Momjian wrote: > An explicit sentence stating that major upgrades can skip major versions is > >> needed.  The document is written assuming the reading knows this, and just > >> makes a few minor notes on the

Re: Upgrading from 11 to 13

On 2021-Apr-02, Koen De Groote wrote: > I seem to recall that going from 11 to 12, a certain configuration file was > removed and the keys are now expected to be set in the regular > configuration file? The logic being there should only ever be 1 > configuration file. > > I can't find it, but at

Re: Upgrading from 11 to 13

I seem to recall that going from 11 to 12, a certain configuration file was removed and the keys are now expected to be set in the regular configuration file? The logic being there should only ever be 1 configuration file. I can't find it, but at the same time I don't recall what it's called. I be

Re: Upgrading from 11 to 13

On 4/1/21 6:06 PM, Bruce Momjian wrote: An explicit sentence stating that major upgrades can skip major versions is >> needed.  The document is written assuming the reading knows this, and just >> makes a few minor notes on the topic: >> e.g., "If you are upgrading across several major versions, be

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 08:30:00AM -0700, David G. Johnston wrote: > On Tue, Mar 30, 2021 at 8:25 AM Daniel Westermann (DWE) < > daniel.westerm...@dbi-services.com> wrote: > The best place would be the release notes, I guess. Right at the beginning > here: > > Release notes are probably a

Re: Upgrading from 11 to 13

On 3/30/21 10:51 AM, Ron wrote: On 3/30/21 9:53 AM, Daniel Westermann (DWE) wrote: On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: Hi, Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit :   I am currently using PostgreSQL 11.2 and would like to try and upgrade it   

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 12:51:50PM -0500, Ron wrote: > On 3/30/21 9:53 AM, Daniel Westermann (DWE) wrote: > > > On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: > > > > Hi, > > > > > > > > Le mar. 30 mars 2021 à 16:10, Susan Joseph a > > > > écrit : > > > > > > > > I am

Re: Upgrading from 11 to 13

On 3/30/21 9:53 AM, Daniel Westermann (DWE) wrote: On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: Hi, Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit : I am currently using PostgreSQL 11.2 and would like to try and upgrade it to the latest version 13.  Can I

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 03:25:06PM +, Daniel Westermann (DWE) wrote: > >On Tue, Mar 30, 2021 at 08:10:08AM -0700, Adrian Klaver wrote: > >> On 3/30/21 8:06 AM, Bruce Momjian wrote: > >> > What other software needs to upgrade through all intermediate versions? > >> > >> Many variations of OS'es

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 8:25 AM Daniel Westermann (DWE) < daniel.westerm...@dbi-services.com> wrote: > >On Tue, Mar 30, 2021 at 08:10:08AM -0700, Adrian Klaver wrote: > >> On 3/30/21 8:06 AM, Bruce Momjian wrote: > >> > What other software needs to upgrade through all intermediate > versions? > >>

Re: Upgrading from 11 to 13

>On Tue, Mar 30, 2021 at 08:10:08AM -0700, Adrian Klaver wrote: >> On 3/30/21 8:06 AM, Bruce Momjian wrote: >> > What other software needs to upgrade through all intermediate versions? >> >> Many variations of OS'es, though not all. One of the benefits of Ubuntu is >> that you can jump from x.LTS

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 08:10:08AM -0700, Adrian Klaver wrote: > On 3/30/21 8:06 AM, Bruce Momjian wrote: > > What other software needs to upgrade through all intermediate versions? > > Many variations of OS'es, though not all. One of the benefits of Ubuntu is > that you can jump from x.LTS to y.L

Re: Upgrading from 11 to 13

On 3/30/21 8:06 AM, Bruce Momjian wrote: On Tue, Mar 30, 2021 at 02:53:10PM +, Daniel Westermann (DWE) wrote: On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: Hi, Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit : I am currently using PostgreSQL 11.2 and would

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 02:53:10PM +, Daniel Westermann (DWE) wrote: > > >On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: > >> Hi, > >> > >> Le mar. 30 mars 2021 à 16:10, Susan Joseph a > >> écrit : > >> > >> I am currently using PostgreSQL 11.2 and would like to try

Re: Upgrading from 11 to 13

>On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: >> Hi, >> >> Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit  >> : >> >> I am currently using PostgreSQL 11.2 and would like to try and upgrade it >> to the latest version 13.  Can I go straight from 11 to 13 or do I

Re: Upgrading from 11 to 13

On 3/30/21 7:09 AM, Susan Joseph wrote: I am currently using PostgreSQL 11.2 and would like to try and upgrade it to the latest version 13.  Can I go straight from 11 to 13 or do I need to upgrade to 12 first and then to 13? You can do this using either dump/restore or pg_upgrade. The importan

Re: Upgrading from 11 to 13

On Tue, Mar 30, 2021 at 04:34:34PM +0200, Guillaume Lelarge wrote: > Hi, > > Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit : > > I am currently using PostgreSQL 11.2 and would like to try and upgrade it > to the latest version 13.  Can I go straight from 11 to 13 or do I need to >

Re: Upgrading from 11 to 13

Hi, Le mar. 30 mars 2021 à 16:10, Susan Joseph a écrit : > I am currently using PostgreSQL 11.2 and would like to try and upgrade it > to the latest version 13. Can I go straight from 11 to 13 or do I need to > upgrade to 12 first and then to 13? > You can go straight to 13. Regards.

Re: Upgrading from 9.6 to 12

On 1/15/20 8:19 AM, Kasun Kulathunga wrote: Hello, We're currently in the beginning phases of a project to upgrade our Postgres cluster from 9.6 to a newer version (most likely v12). This is actually going to be a two part move since we're going to move from a RHEL-backed cluster to an Ubunt

Re: Upgrading from PostgreSQL 9.3 to 11.6

On 2019-12-20 09:02, Justin wrote: Hi Tony Can you describe the database in greater detail? how many tables, type of data, how big is the down time window? So this will be on new server hardware, and new DB install, what OS? and extensions being used, has there been any testing with apps

Re: Upgrading from PostgreSQL 9.3 to 11.6

On 12/20/19 5:58 AM, t...@exquisiteimages.com wrote: I have a PostgreSQL 9.3 installation that I finally have time to migrate to a currently supported version. The server that the installation is installed on is also at its end of service. Can anyone help me with completing this conversion as

Re: Upgrading from V11 to V12 on Debian install

On 12/2/19 11:28 AM, stan wrote: I have several machines that have version 11 instances on them. These are all Debian or Ubuntu machines. All of them are pointed to the Postgres repositories fro the Postgres binaries deb http://apt.postgresql.org/pub/repos/apt/ buster-pgdg main dpkg -l shows:

Re: Upgrading old server

El 25/9/19 a las 20:21, Adrian Klaver escribió: On 9/25/19 9:00 AM, Tom Lane wrote: Ron writes: On 9/25/19 9:29 AM, Christoph Berg wrote: Re: Ekaterina Amez 2019-09-25 <8818b028-bd2d-412e-d4e3-e29c49ffe...@zunibal.com> We've decided to upgrade our PostgreSQL production servers. First task i

Re: Upgrading old server

On 9/25/19 9:00 AM, Tom Lane wrote: Ron writes: On 9/25/19 9:29 AM, Christoph Berg wrote: Re: Ekaterina Amez 2019-09-25 <8818b028-bd2d-412e-d4e3-e29c49ffe...@zunibal.com> We've decided to upgrade our PostgreSQL production servers. First task is remove an old v7.14 version. It was supposed to

Re: Upgrading old server

Ron writes: > On 9/25/19 9:29 AM, Christoph Berg wrote: >> Re: Ekaterina Amez 2019-09-25 >> <8818b028-bd2d-412e-d4e3-e29c49ffe...@zunibal.com> >>> We've decided to upgrade our PostgreSQL production servers. First task is >>> remove an old v7.14 version. It was supposed to be upgraded to a v8.4 >>

Re: Upgrading old server

On 9/25/19 9:29 AM, Christoph Berg wrote: Re: Ekaterina Amez 2019-09-25 <8818b028-bd2d-412e-d4e3-e29c49ffe...@zunibal.com> We've decided to upgrade our PostgreSQL production servers. First task is remove an old v7.14 version. It was supposed to be upgraded to a v8.4 server. The server was instal

Re: Upgrading old server

Re: Ekaterina Amez 2019-09-25 <8818b028-bd2d-412e-d4e3-e29c49ffe...@zunibal.com> > We've decided to upgrade our PostgreSQL production servers. First task is > remove an old v7.14 version. It was supposed to be upgraded to a v8.4 > server. The server was installed, several databases where released h

Re: Upgrading 9.1.17 to which version?

>Get a second machine, set it up to be as identical to the existing machine as >you can - aside from it not >being near death - and migrate "production" to it. >  >Then on the machine described above install v10 and whatever else you need for >staging/testing and then >once everything checks ou

Re: Upgrading 9.1.17 to which version?

>>I spent most of yesterday trying to get 9.6.13 installed from the PostgreSQL >>Yum repository and finally >>got it working with the initdb stuff stored on a >>non-default dedicated partition (RAID10 array) only to >>find that psql >>didn't work and was complaining about a missing libpq.so.5.

Re: Upgrading 9.1.17 to which version?

On 5/16/19 10:38 AM, Fabio Ugo Venchiarutti wrote: 11.x would be best, since it's EOL is furthest in the future. 9.6 would be best, because it's had more bug-fix releases. Aren't all important bugfixes backported to every non-EOL affected majors at once? Correct me if I'm wrong but I

Re: Upgrading 9.1.17 to which version?

On Thu, May 16, 2019 at 10:38 AM Fabio Ugo Venchiarutti < f.venchiaru...@ocado.com> wrote: > On 16/05/2019 18:20, Ron wrote: > > On 5/16/19 4:36 AM, nigel.ander...@gmx.com wrote: > >> but I wonder whether that might be an easier/more reliable option from > >> an install and point of view and certa

Re: Upgrading 9.1.17 to which version?

On 16/05/2019 18:20, Ron wrote: On 5/16/19 4:36 AM, nigel.ander...@gmx.com wrote: Hi, I've just inherited an ancient install of 9.1.17 after our tech guy left, on what turns out to be a rapidly dying server and being a total newb to PostgreSQL (and not much more advanced on Linux) I'm a lit

Re: Upgrading 9.1.17 to which version?

On 5/16/19 4:36 AM, nigel.ander...@gmx.com wrote: Hi, I've just inherited an ancient install of 9.1.17 after our tech guy left, on what turns out to be a rapidly dying server and being a total newb to PostgreSQL (and not much more advanced on Linux) I'm a little stuck on the way ahead. I've ma

Re: Upgrading 9.1.17 to which version?

On Thu, May 16, 2019 at 9:36 AM wrote: > Hi, > > I've just inherited an ancient install of 9.1.17 after our tech guy left, > on what turns out to be a rapidly dying server and being a total newb to > PostgreSQL (and not much more advanced on Linux) I'm a little stuck on the > way ahead. > > I've

Re: Upgrading locale issues

On 2019-05-03 15:35, Daniel Verite wrote: > 'b' < 'a' is never true for any locale AFAIK, But there is 'bb' < 'aa' in Danish. :-) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Re: Upgrading locale issues

On Wed, May 1, 2019 at 3:09 PM Thomas Munro wrote: > As discussed over on -hackers[1], I think it's worth pursuing that > though. FWIW I've proposed locale versioning for FreeBSD's libc[2]. > The reason I haven't gone further with that yet even though the code > change has been accepted in princi

Re: Upgrading locale issues

rihad wrote: > On 05/03/2019 05:35 PM, Daniel Verite wrote: > > For non-English text, I would recommend C.UTF-8 over "C" because of > > BTW, there's no C.UTF-8 inside pg_collation, and running select > pg_import_system_collations('pg_catalog') doesn't bring it in, at least > not on Free

Re: Upgrading locale issues

On 05/03/2019 05:35 PM, Daniel Verite wrote: For non-English text, I would recommend C.UTF-8 over "C" because of BTW, there's no C.UTF-8 inside pg_collation, and running select pg_import_system_collations('pg_catalog') doesn't bring it in, at least not on FreeBSD 11.2.

Re: Upgrading locale issues

On 05/03/2019 05:35 PM, Daniel Verite wrote: rihad wrote: Thanks, I'm a bit confused here. AFAIK indexes are used for at least two things: for speed and for skipping the ORDER BY step (since btree indexes are already sorted). Will such an "upgrade-immune" C.UTF-8 index still work correc

Re: Upgrading locale issues

rihad wrote: > Thanks, I'm a bit confused here. AFAIK indexes are used for at least two > things: for speed and for skipping the ORDER BY step (since btree > indexes are already sorted). Will such an "upgrade-immune" C.UTF-8 index > still work correctly for table lookups? If the lookup

Re: Upgrading locale issues

On 05/02/2019 05:36 PM, Daniel Verite wrote: rihad wrote: Thanks for the reply. Do you know what would a "decent" ICU collation be to bind to a field's schema definition so it would mimic a UTF-8 encoding for a multilingual column? Maybe und-x-icu? We aren't as much concerned about thei

Re: Upgrading locale issues

rihad wrote: > Thanks for the reply. Do you know what would a "decent" ICU collation be > to bind to a field's schema definition so it would mimic a UTF-8 > encoding for a multilingual column? Maybe und-x-icu? We aren't as much > concerned about their sortability in most cases, we just

  1   2   >