Skip to content

feat: run clones with custom port and socket dir

Artyom Kartasov requested to merge update-clone-image into master

Description

Run clones with custom port and socket directory to be able to restart or upgrade Postgres instance without losing container

This change is not backward compatible to the previous versions of the extended images

Related issue

Examples

root@d028e0df514a:/# ps fax
    PID TTY      STAT   TIME COMMAND
     29 pts/0    Ss     0:00 bash
    518 pts/0    R+     0:00  \_ ps fax
      1 ?        Ss     0:00 /bin/bash /pg_start.sh
      8 ?        S      0:00 sudo -Eu postgres /usr/lib/postgresql/14/bin/postgres -D /var/lib/dblab/oldest5/clones/dblab_clone_6001/data -k /var/lib/dblab/oldest5/sockets/dblab_clone_6001 -p 6001
      9 ?        S      0:00  \_ /usr/lib/postgresql/14/bin/postgres -D /var/lib/dblab/oldest5/clones/dblab_clone_6001/data -k /var/lib/dblab/oldest5/sockets/dblab_clone_6001 -p 6001
     10 ?        Ss     0:00      \_ postgres: logger 
     12 ?        Ss     0:00      \_ postgres: checkpointer 
     13 ?        Ss     0:00      \_ postgres: background writer 
     14 ?        Ss     0:00      \_ postgres: walwriter 
     15 ?        Ss     0:00      \_ postgres: autovacuum launcher 
     16 ?        Ss     0:00      \_ postgres: stats collector 
     17 ?        Ss     0:00      \_ postgres: logical replication launcher 

Checklist

  • MR description has been reviewed
  • MR changes are functionally tested
  • MR does NOT have API/CLI changes OR there are API/CLI changes and they have been reviewed & DOCS ARE ADJUSTED (reference doc, etc)
  • MR does NOT have UI changes OR there are UI changes and they have been reviewed & UX IS REVIEWED

Merge request reports