Click here to Skip to main content
15,887,585 members

Welcome to the Lounge

   

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

 
GeneralRe: The weird, wasteful world of IoT Pin
honey the codewitch6-Jun-22 1:00
mvahoney the codewitch6-Jun-22 1:00 
GeneralRe: The weird, wasteful world of IoT Pin
Daniel Pfeffer6-Jun-22 7:10
professionalDaniel Pfeffer6-Jun-22 7:10 
GeneralRe: The weird, wasteful world of IoT Pin
honey the codewitch6-Jun-22 7:12
mvahoney the codewitch6-Jun-22 7:12 
GeneralRe: The weird, wasteful world of IoT Pin
Peter Shaw8-Jun-22 9:45
professionalPeter Shaw8-Jun-22 9:45 
GeneralThe pg_upgrade blues Pin
RickZeeland3-Jun-22 22:56
mveRickZeeland3-Jun-22 22:56 
GeneralRe: The pg_upgrade blues Pin
honey the codewitch3-Jun-22 23:54
mvahoney the codewitch3-Jun-22 23:54 
GeneralRe: The pg_upgrade blues Pin
RickZeeland4-Jun-22 0:06
mveRickZeeland4-Jun-22 0:06 
GeneralRe: The pg_upgrade blues Pin
Peter Shaw8-Jun-22 10:06
professionalPeter Shaw8-Jun-22 10:06 
Having upgraded from earlier versions of postgres since at least v 7.1, the way I have always found is the easiest way to do it, no matter what the platform is as follows:

1) Install the new version that you want to upgrade too, in a different location (File system wise) and listening on a different TCP port to the old instance.

2) Configure the Postgres pg_hba.conf file to allow the terminal your working from full access (The MD5 warnings are valid here), MD5 is fine if the server is not exposed to the internet as you are only allowing this access for the duration of the upgrade, if you make the access address have an IP V4 address with a 32 bit mask, no one except your workstation will be able to access it anyway...

3) Configure an second access in pg_hba.conf that allows the IP address of the already running older postgres server to also access the new one.

4) use "pg_dump -U postgres -h oldpgip -p oldpgport dbname | psql -U postgres -h newpgip -p newpgport dbname" to copy directly from the old DB to the new DB, make sure that ALL apps using the old db are shut down and inactive before you do this.

5) Wait.... possibly a long time.... I usually do things like this overnight....

6) Once the transfer is complete, shut down the old instance and remove it (After first testing the new instance has the data in it etc) then if you desire configure the new instance to have be on the same port/IP etc as the old one.

This trick will work on a machine where both servers are on the same machine, and that's even better because you can then just assign the pg_hba entries with IP=127.0.0.1/32 with trust authentication, then use the PG command line tools on the same box. Just make sure you configure the data directories to be separate from each other.

This is great in another respect too, because as long as you have the required add on extensions installed for the new version (EG: PostGIS) then this will transfer across all the required statements to re-add user accounts, extension objects, data types you name it.

PraiseRe: The pg_upgrade blues Pin
RickZeeland8-Jun-22 19:16
mveRickZeeland8-Jun-22 19:16 
GeneralRe: The pg_upgrade blues Pin
Peter Shaw9-Jun-22 3:31
professionalPeter Shaw9-Jun-22 3:31 
GeneralWordle 350 Pin
Amarnath S3-Jun-22 14:33
professionalAmarnath S3-Jun-22 14:33 
GeneralRe: Wordle 350 Pin
Peter_in_27803-Jun-22 16:09
professionalPeter_in_27803-Jun-22 16:09 
GeneralRe: Wordle 350 Pin
OriginalGriff3-Jun-22 18:41
mveOriginalGriff3-Jun-22 18:41 
GeneralRe: Wordle 350 Pin
0x01AA3-Jun-22 20:57
mve0x01AA3-Jun-22 20:57 
GeneralRe: Wordle 350 Pin
pkfox3-Jun-22 21:30
professionalpkfox3-Jun-22 21:30 
GeneralRe: Wordle 350 Pin
Sander Rossel3-Jun-22 21:57
professionalSander Rossel3-Jun-22 21:57 
GeneralRe: Wordle 350 Pin
0x01AA4-Jun-22 1:01
mve0x01AA4-Jun-22 1:01 
GeneralRe: Wordle 350 Pin
Sander Rossel5-Jun-22 3:16
professionalSander Rossel5-Jun-22 3:16 
GeneralRe: Wordle 350 Pin
Vivi Chellappa3-Jun-22 22:05
professionalVivi Chellappa3-Jun-22 22:05 
GeneralRe: Wordle 350 Pin
Greg Utas4-Jun-22 0:18
professionalGreg Utas4-Jun-22 0:18 
GeneralRe: Wordle 350 Pin
Peter_in_27804-Jun-22 0:54
professionalPeter_in_27804-Jun-22 0:54 
GeneralRe: Wordle 350 Pin
FreedMalloc4-Jun-22 5:19
FreedMalloc4-Jun-22 5:19 
GeneralRe: Wordle 350 Pin
Greg Utas4-Jun-22 5:27
professionalGreg Utas4-Jun-22 5:27 
GeneralRe: Wordle 350 Pin
FreedMalloc4-Jun-22 5:51
FreedMalloc4-Jun-22 5:51 
GeneralRe: Wordle 350 Pin
Greg Utas4-Jun-22 6:01
professionalGreg Utas4-Jun-22 6:01 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.