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: Table : Bloat grow high

On 2022-11-12 08:24:23 -0600, Ron wrote: > On 11/12/22 08:05, Laurenz Albe wrote: > You'd be most happy with HOT updates. Make sure that there is no index > on any of > the columns you update, and change the table to have a "fillfactor" less > than > 100. Then you can get HOT update

Re: Table : Bloat grow high

On 11/12/22 08:05, Laurenz Albe wrote: On Fri, 2022-11-11 at 17:09 +, Alexis Zapata wrote: In postgresql 13.5 I have a table (size 3.1 GB) and in this table occurs near to 200 updates per second, after 2 days the size table is 7 GB and bloat grow to 45% and  the query operations are degrad

Re: Table : Bloat grow high

On Fri, 2022-11-11 at 17:09 +, Alexis Zapata wrote: > In postgresql 13.5 I have a table (size 3.1 GB) and in this table occurs near > to > 200 updates per second, after 2 days the size table is 7 GB and bloat grow to > 45% and >  the query operations are degraded. vacuum runs every 5 seconds

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/