RE: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

October 30, 2024 12:06 AM To: Daniel Gustafsson ; 馬　騰飛 Cc: pgsql-general@lists.postgresql.org Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3 CAUTION：This is an external email. Please be cautious when opening links or attachments in email.

Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

offer any advice, but it sounds like the problems is that the server wants to use SCRAM passwords and your version of npgsql only support cleartext and md5. Changing the METHOD in pg_hba.conf to md5 could fix the immediate problem perhaps but upgrading to a version that support SCRAM seems the most a

Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

er any advice, but it sounds like the problems is that the server wants to use SCRAM passwords and your version of npgsql only support cleartext and md5. Changing the METHOD in pg_hba.conf to md5 could fix the immediate problem perhaps but upgrading to a version that support SCRAM seems the m

RE: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

-general@lists.postgresql.org Subject: Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3 CAUTION：This is an external email. Please be cautious when opening links or attachments in email. > On 25 Oct 2024, at 05:45, 馬　騰飛 wrote: > > Dear P

Re: Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

> On 25 Oct 2024, at 05:45, 馬　騰飛 wrote: > > Dear PostgreSQL Community, > > After upgrading PostgreSQL to version 16.3, our server encountered the error > "Only AuthenticationClearTextPassword and AuthenticationMD5Password supported > for now. Received: 10"

Compatibility Issues with Npgsql and .NET Framework 3.5 after Upgrading to PostgreSQL 16.3

Dear PostgreSQL Community, After upgrading PostgreSQL to version 16.3, our server encountered the error "Only AuthenticationClearTextPassword and AuthenticationMD5Password supported for now. Received: 10" when connecting to the database. We are currently using .NET Framework version

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

Upgrading from v12.7 to v15.7

Hello Engineers, After upgrading from v12.7 to v15.7, I ran the following command and got this error message. postgres_upgrade_work_area]$ /usr/pgsql-15/bin/pg_upgrade \ > --check \ --old-datadir=/data/postgres12 \ > --old-datadir=/data/postgres12 \ > --new-datadir=/data/postgres \ >

Re: Seeing new stuff in log after upgrading from 11 to 15

Thanks for the quick reply! NP, I was just being extra cautious after upgrade. From: Tom Lane Sent: Wednesday, May 15, 2024 6:50 PM To: Dmitry O Litvintsev Cc: pgsql-general@lists.postgresql.org Subject: Re: Seeing new stuff in log after upgrading from

Re: Seeing new stuff in log after upgrading from 11 to 15

Dmitry O Litvintsev writes: > After upgrade 11 -> 15 started to see these messages in hot standby log: > < 2024-05-15 17:20:24.164 CDT 151879 > LOG: restartpoint complete: wrote > 296338 buffers (28.3%); 0 WAL file(s) added, 134 removed, 0 recycled; > write=1619.469 s, sync=0.022 s, total=161

Seeing new stuff in log after upgrading from 11 to 15

Hi, After upgrade 11 -> 15 started to see these messages in hot standby log: < 2024-05-15 17:20:24.164 CDT 151879 > LOG: restartpoint complete: wrote 296338 buffers (28.3%); 0 WAL file(s) added, 134 removed, 0 recycled; write=1619.469 s, sync=0.022 s, total=1619.539 s; sync files=1492, long

RE: Performance degradation after upgrading from 9.5 to 14

På lørdag 27. april 2024 kl. 11:46:26, skrev Zahir Lalani < ZahirLalani@oliver.agency >: Same issue and took us ages to work out that is was JIT! The default is on, and setting off solves the problem. I have seen several blogs reporting the same and so wonder

RE: Performance degradation after upgrading from 9.5 to 14

-generallists.postgresql.org Subject: Re: Performance degradation after upgrading from 9.5 to 14 You don't often get email from aleksandr.ja...@privatbank.ua<mailto:aleksandr.ja...@privatbank.ua>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> CAUTION: This

Re: Performance degradation after upgrading from 9.5 to 14

On Tue, 23 Apr 2024 at 07:01, Олександр Янін wrote: > Try setting enable_memoize to off. > Our practice has shown that enabling this parameter by default often resulted > in less than optimal query plans in the cache. It would be good to see a thread opened with details on this. I understand in

Re: Performance degradation after upgrading from 9.5 to 14

Try setting enable_memoize to off. Our practice has shown that enabling this parameter by default often resulted in less than optimal query plans in the cache. ср, 17 апр. 2024 г. в 20:13, Johnathan Tiamoh : > Hello, > > > I performed an upgrade from postgresql-9.5 to postgresql-14 and the > pe

Re: Performance degradation after upgrading from 9.5 to 14

I'm not sure, does it helps you but read this: https://www.cybertec-postgresql.com/en/b-tree-index-improvements-in-postgresql-v12/ "Since upgrading with pg_upgrade does not change the data files, indexes will still be in version 3 after an upgrade" I reindexed all my database, when

Re: Performance degradation after upgrading from 9.5 to 14

how about this: jit = off ? Marcin On Wed, 17 Apr 2024 at 19:33, Johnathan Tiamoh wrote: > 1) How did you upgrade? pg_dump or pg_upgrade? > > I use pg_ugrade with kink option. > > 2) Did you run ANALYZE to collect statistics after the upgrade? > > > Yes. I ran vacuumdb-analyze in stages after

Re: Performance degradation after upgrading from 9.5 to 14

1) How did you upgrade? pg_dump or pg_upgrade? I use pg_ugrade with kink option. 2) Did you run ANALYZE to collect statistics after the upgrade? Yes. I ran vacuumdb-analyze in stages after the upgrade 3) Did you transfer the configuration, or did you just create a new cluster with the default

Re: Performance degradation after upgrading from 9.5 to 14

> On Apr 17, 2024, at 10:13, Johnathan Tiamoh wrote: > I performed an upgrade from postgresql-9.5 to postgresql-14 and the > performance has degraded drastically. > > Please, is they any advice on getting performance back ? Run: VACUUM (ANALYZE, VERBOSE); More seriously (although

Re: Performance degradation after upgrading from 9.5 to 14

On 4/17/24 19:13, Johnathan Tiamoh wrote: > Hello, > > > I performed an upgrade from postgresql-9.5 to postgresql-14 and the > performance has degraded drastically. > > Please, is they any advice on getting performance back ? > There's very little practical advice we can provide based on this

Performance degradation after upgrading from 9.5 to 14

Hello, I performed an upgrade from postgresql-9.5 to postgresql-14 and the performance has degraded drastically. Please, is they any advice on getting performance back ? King Regards Johnathan T.

Fwd: Getting error while upgrading

On Sat, Mar 9, 2024 at 12:18 PM omkar narkar wrote: > Hello Team, > > I am trying to upgrade my edb 10.5 community version to postgres 15.6 > version and while doing this i am getting error regarding OIDS are not > stable across Postgresql version (sys.callback_queue_table.user_data). > Kindly he

Getting error while upgrading

Hello Team, I am trying to upgrade my edb 10.5 community version to postgres 15.6 version and while doing this i am getting error regarding OIDS are not stable across Postgresql version (sys.callback_queue_table.user_data). Kindly help me to get the solution of this issue. Thanks and regards, Omk

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

Upgrading

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? Thanks in advance.

Re: Problem perhaps after upgrading to pgadmin4 7.4

On 7/13/23 06:20, Carl Erik Eriksson wrote: Query tool PGadmin on my mac If I enter a query like select count(*) from table_1I get a correct response from the server If I enter select * from table_1 I get an error message that I do not understand: Error Message:missing FROM-clause entry f

Re: Problem perhaps after upgrading to pgadmin4 7.4

> On 13/07/2023 13:20 CEST Carl Erik Eriksson wrote: > > Query tool PGadmin on my mac > > If I enter a query like select count(*) from table_1I get a correct > response from the server > If I enter select * from table_1 I get an error message that I do not > understand: > Error Message:missin

Re: Problem perhaps after upgrading to pgadmin4 7.4

Problem solved - thanks Depez! (The solution for now is to downgrade to PGadmin4 version 7.2) > On 13 Jul 2023, at 13:52, hubert depesz lubaczewski wrote: > > On Thu, Jul 13, 2023 at 01:20:03PM +0200, Carl Erik Eriksson wrote: >> If I enter a query like select count(*) from table_1I get

Re: Problem perhaps after upgrading to pgadmin4 7.4

Thanks - it seems we might be on pg 10.17-1 /Carl > On 13 Jul 2023, at 13:52, hubert depesz lubaczewski wrote: > > On Thu, Jul 13, 2023 at 01:20:03PM +0200, Carl Erik Eriksson wrote: >> If I enter a query like select count(*) from table_1I get a correct >> response from the server >> If I

Re: Problem perhaps after upgrading to pgadmin4 7.4

On Thu, Jul 13, 2023 at 01:20:03PM +0200, Carl Erik Eriksson wrote: > If I enter a query like select count(*) from table_1I get a correct > response from the server > If I enter select * from table_1 I get an error message that I do not > understand: > Error Message:missing FROM-clause entry

Problem perhaps after upgrading to pgadmin4 7.4

Query tool PGadmin on my mac If I enter a query like select count(*) from table_1I get a correct response from the server If I enter select * from table_1 I get an error message that I do not understand: Error Message:missing FROM-clause entry for table "rel" LINE 8: ...ER JOIN pg_catalog.p

Re: Re[2]: Getting error while upgrading postgres from version 12 to 13

On Tue, 21 Mar 2023 at 16:06, Geoff Winkless wrote: > On Tue, 21 Mar 2023 at 10:29, shashidhar Reddy < > shashidharreddy...@gmail.com> wrote: > >> Actually I was using the below command to check the compatibility, it >> worked without any issue with 12.6 but it is not working with 1version 2.14 >

Re: Re[2]: Getting error while upgrading postgres from version 12 to 13

On Tue, 21 Mar 2023 at 10:29, shashidhar Reddy wrote: > Actually I was using the below command to check the compatibility, it > worked without any issue with 12.6 but it is not working with 1version 2.14 > time /usr/lib/postgresql/13/bin/pg_upgrade --old-bindir > /usr/lib/postgresql/12/bin --new-

Re: Getting error while upgrading postgres from version 12 to 13

On 3/21/23 08:13, shashidhar Reddy wrote: Both shows different versions as 13 shows version 13.10 and 12 shows 12. The question asked was: "Check the value that is the PG_VERSION file in each data directory. It should be 12 in /usr/pgdata/pg_data and 13 in /usr/pgdata/pg_data2." So indicate w

Re: Getting error while upgrading postgres from version 12 to 13

Both shows different versions as 13 shows version 13.10 and 12 shows 12.14 On Tue, 21 Mar, 2023, 8:09 pm Adrian Klaver, wrote: > On 3/21/23 03:29, shashidhar Reddy wrote: > > Actually I was using the below command to check the compatibility, it > > worked without any issue with 12.6 but it is no

Re: Getting error while upgrading postgres from version 12 to 13

On 3/21/23 03:29, shashidhar Reddy wrote: Actually I was using the below command to check the compatibility, it worked without any issue with 12.6 but it is not working with 1version 2.14 time /usr/lib/postgresql/13/bin/pg_upgrade --old-bindir /usr/lib/postgresql/12/bin --new-bindir /usr/lib/pos

Re: Re[2]: Getting error while upgrading postgres from version 12 to 13

Actually I was using the below command to check the compatibility, it worked without any issue with 12.6 but it is not working with 1version 2.14 time /usr/lib/postgresql/13/bin/pg_upgrade --old-bindir /usr/lib/postgresql/12/bin --new-bindir /usr/lib/postgresql/13/bin --old-datadir /usr/pgdata/pg_d

Re[2]: Getting error while upgrading postgres from version 12 to 13

Hello, As per error it seems you have initiated source data with PG13 binaries.  Could you please connect to both source and target psql and share out of select versions(); Also share pg_upgrade complete command which you are using.  Regards, Abdul Sayeed Sent from myMail for iOS Sunda

Re: Getting error while upgrading postgres from version 12 to 13

On Sat, Mar 18, 2023 at 7:27 PM shashidhar Reddy < shashidharreddy...@gmail.com> wrote: > Can someone please help me with this? > >> >> You haven't given others enough information to help you. Present to the fullest extent possible your current environment and the commands you are running. Showi

Re: Getting error while upgrading postgres from version 12 to 13

FATAL:  could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": key values mismatch On Sun, Mar 19, 2023 at 2:09 AM shashidhar Reddy mailto:shashidharreddy...@gmail.com>> wrote: Hello, I am in a process of upgrading postgresql fro

Re: Getting error while upgrading postgres from version 12 to 13

rivate key file > "/etc/ssl/private/ssl-cert-snakeoil.key": key values mismatch > > On Sun, Mar 19, 2023 at 2:09 AM shashidhar Reddy < > shashidharreddy...@gmail.com> wrote: > >> Hello, >> >> I am in a process of upgrading postgresql from version 12 to 13 u

Re: Getting error while upgrading postgres from version 12 to 13

On Sun, Mar 19, 2023 at 2:09 AM shashidhar Reddy mailto:shashidharreddy...@gmail.com>> wrote: Hello, I am in a process of upgrading postgresql from version 12 to 13 using pg_upgrdrade but I am getting error stating  FATAL:  database files are incompatible with

Re: Getting error while upgrading postgres from version 12 to 13

On 18.03.23 22:24, shashidhar Reddy wrote: and adding to this the following is also showing in the error, we tried changing the file permissions but still no luck FATAL:  could not load private key file "/etc/ssl/private/ssl-cert-snakeoil.key": key values mismatch This sounds like the private

Re: Getting error while upgrading postgres from version 12 to 13

ashidharreddy...@gmail.com> wrote: > Hello, > > I am in a process of upgrading postgresql from version 12 to 13 using > pg_upgrdrade but I am getting error stating > > FATAL: database files are incompatible with server > DETAIL: The data directory was initialized by PostgreSQL v

Re: Getting error while upgrading postgres from version 12 to 13

On 3/18/23 15:39, shashidhar Reddy wrote: Hello, I am in a process of upgrading postgresql from version 12 to 13 using pg_upgrdrade but I am getting error stating  FATAL:  database files are incompatible with server  DETAIL:  The data directory was initialized by PostgreSQL version 13

Getting error while upgrading postgres from version 12 to 13

Hello, I am in a process of upgrading postgresql from version 12 to 13 using pg_upgrdrade but I am getting error stating FATAL: database files are incompatible with server DETAIL: The data directory was initialized by PostgreSQL version 13 , which is not compatible with this version 12.14

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 agai

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

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_up

Upgrading to v12

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? Q2: I get this error, and then at the end, it says "No erro

Re: Error while upgrading from v12 to v13

I have dropped the function on all databases on version 12,but while upgrading I am still getting the same error On Sat, 29 Oct, 2022, 7:56 pm Imre Samu, wrote: > > ERROR: could not find function "pl_profiler_enable" in file > > maybe obsolete function? > > -- D

Re: Error while upgrading from v12 to v13

2022. okt. 29., Szo, 13:40): > > I am getting below error while upgrading postgres from version 12 to 13 > and not sure how to enable the function before upgrading the cluster. Can > you please help me to resolve this. > > error: could not execute query: ERROR: could not find fun

Re: Error while upgrading from v12 to v13

Any help in this? On Sat, 29 Oct, 2022, 5:09 pm shashidhar Reddy, < shashidharreddy...@gmail.com> wrote: > > I am getting below error while upgrading postgres from version 12 to 13 > and not sure how to enable the function before upgrading the cluster. Can > you please help

Error while upgrading from v12 to v13

I am getting below error while upgrading postgres from version 12 to 13 and not sure how to enable the function before upgrading the cluster. Can you please help me to resolve this. error: could not execute query: ERROR: could not find function "pl_profiler_enable" in file "/usr

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 >

Upgrading error

Hi, I have a postgresql server version 12.9 and trying to upgrade it to 14.5. My OS is Centos 8 Stream and I already managed to install postgresql14.5 but when I'm trying to upgrade, I am encountering this error bash-4.4$ /usr/pgsql-14/bin/pg_upgrade --old-datadir=/home/dmartuser/pgdata/data/ --n

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

Upgrading from 12.3 to 12.11

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 1211 and run that to upgrade the product and still maintain access to the existing connections?Sent from my Verizo

Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters

From: Laurenz Albe Sent: Wednesday, July 13, 2022 3:16 AM > You configured "pg_hba.conf" so that a local login without password is > not possible.  The easiest solution is to change the "pg_hba.conf" > entries for "localhost" in IPv4 and IPv6 to "trust" for the duration of > the upgrade. I am af

Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters

On Wed, 2022-07-13 at 02:53 +, Ken Yeung wrote: > From: Laurenz Albe > Sent: Wednesday, July 13, 2022 3:16 AM > > > You configured "pg_hba.conf" so that a local login without password is > > not possible.  The easiest solution is to change the "pg_hba.conf" > > entries for "localhost" in IPv4

  1   2   3   4   >